| === mimir|zZz is now known as mimir|work | ||
| === mimir|work is now known as mimir | ||
| === mimir is now known as mimir|on | ||
| jdbrowne | Hello, why debian packages must be built as root? (or with fakeroot ...) | 09:43 |
|---|---|---|
| jdbrowne | There are a number of targets in the default debian/rules generated by dh_make, how do I know which ones are mandatory and which ones are not? I guess "clean", "install" and "binary" are mandatory but I may be missing something. | 10:03 |
| joaopinto | jdbrowne, debian packages must not and should not be build as root | 10:14 |
| jdbrowne | Ok, why does the dpkg-buildpackage has the option "-r gain-root-command"? there must be some use case I do not see | 10:16 |
| joaopinto | no idea, never needed it | 10:17 |
| jdbrowne | ok | 10:21 |
| james_w | it defaults to fakeroot now | 10:24 |
| james_w | "root" access is needed for certain parts of the build | 10:25 |
| james_w | as for what is mandatory, check debian policy | 10:25 |
| jdbrowne | james_w: for my information, can you give example of parts of the build which need to be root? | 10:28 |
| james_w | that's also in debian policy I believe | 10:28 |
| jdbrowne | ok thx | 10:28 |
| joaopinto | jdbrowne, "root" is required for the "binary" rules, because you want the archive files to be root owned, that is why fakeroot is sufficient, there is no need for real root | 10:32 |
| jdbrowne | Ok thx, I am reading the debian policy, see ya in a while :) | 10:33 |
| joaopinto | see you tomorrow :D | 10:33 |
| jdbrowne | To my question : which target are required in a debian/rules, the answer is in the debian policy : http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules | 11:02 |
| jdbrowne | "At a minimum, required targets are the ones called by dpkg-buildpackage, namely, clean, binary, binary-arch, binary-indep, and build." | 11:02 |
| jdbrowne | I am reading about the optional target "get-orig-source" in the debian/rules. This is powerful, this is a built-in mechanism that makes it possible to streamline package out of sources without having to teach the upstream developpers how to make packages. Packages can be done by some else without refering/disturbing/interfacing with the developers. | 11:20 |
| joaopinto | jdbrowne, except when you have patches or library changes ;) | 11:24 |
| jdbrowne | yes, in our process, this can be done through the bug tracking system, bit by bit | 11:28 |
| === santiago-pgsql is now known as santiago-ve | ||
| jdbrowne | life is good, I have a nice little package for my script. There are now minimal debian/control, debian/rules and a debian/myscript.install. | 15:05 |
| jdbrowne | There is a step that seems unneeded: when I checkout my sources, I would like to be able to execute dpkg-buildpackage but dpkg-buildpackage insists on having a directory name formatted like myscript-<version> and also insist on having an orig.tar.gz. | 15:05 |
| jdbrowne | What are the tools/technique I can use to simply build a package after a checkout? | 15:06 |
| gianni | ciao a tutti | 16:33 |
| === k00011 is now known as k0001 | ||
| === k00011 is now known as k0001 | ||
| === k00011 is now known as k0001 | ||
| === k0001 is now known as testing_somethin | ||
| === testing_somethin is now known as k0001 | ||
| === Andre123 is now known as AndreSTC | ||
| === k00011 is now known as k0001 | ||
| mirak | hi | 20:03 |
| grant__ | Hello | 20:43 |
| maxb | jdbrowne: It does not insist, it merely warns. You may safely ignore. | 21:08 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!