On Fri, Jun 13, 2008 at 02:07:29PM +0000, Jon wrote: > Perhaps you can explain something to me then. > > I am able to build the package without being root, and have explained this > to the user. He just can't get it to work with his command line. > > Please explain why this makes the bug serious? Where does it state in the > policy that -*that*- exact command-line must be supported? > > Jon
Well, You're supposed to know that, and it's so easy to find you
should be ashamed to ask. Though it's in policy §4.9 [0], I quote the
relevant bits:
build
The build target must not do anything that might require root privilege.
build-arch (optional), build-indep (optional)
The build-arch and build-indep targets must not do anything that
might require root privilege.
binary, binary-arch, binary-indep
The binary targets must be invoked as root.[23]
clean
The clean target may need to be invoked as root if binary has been
invoked since the last clean, or if build has been invoked as root
(since build may create directories, for example).
IOW fakeroot must not be used for anything else than the binary* and
clean targets. *FULL STOP*. Anything else is buggy, whatever command
you're using.
IOW, building a debian package this way:
$ dpkg-source -x foo.dsc
$ cd foo*/
$ ./debian/rules build
$ fakeroot debian/rules binary
$ fakeroot debian/rules clean
*must* be supported no matter what. FWIW this is Debian Packaging 101.
[0] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules
--
·O· Pierre Habouzit
··O [EMAIL PROTECTED]
OOO http://www.madism.org
pgpkdq21dg8PU.pgp
Description: PGP signature
