Re: Should debhelper's dh_md5sums and dh_makeshlibs use chown?

[Joey Hess <joey@kitenet.net>]

Jean Pierre LeJacq wrote:
> It comes down to an interpertation of what is the difference between
> "build" and "binary" targets.  The predominant interpertation is the
> build is compile the source and binary to construct debian/tmp.  My
> interpertation is that build compiles the source AND constructs as
> much of debian/tmp as possible without root privileges.  binary then
> completes the debian/tmp construction by executing commands that only
> root can do (i.e. chown).

Hmm, let's take a look at the debian packaging manual, section 3.2.1:

  build
        This should perform all non-interactive configuration and compilation
  of the package. [...]

        The build target must not do anything that might require root
  privilege.

  binary
  
        The binary target should be all that is necessary for the user to
  build the binary package. [...]
  
        Both binary-* targets should depend on the build target, above, so
  that the package is built if it has not been already. It should then create
  the relevant binary package(s), using dpkg-gencontrol to make their control
  files and dpkg-deb to build them and place them in the parent of the top level
  directory.

It does say that build should do configuration and compilation. It doesn't
mention installation. But it does seem to leave the question somewhat open.

I do understand where you're coming from - before fakeroot, my debian/rules
files had a binary-root section, that contained all the things needed to be
run by root. It su'd to root if you wern't already root; this allowed me to
build the package as a normal user, and only become root for as few commands
as possible.

With fakeroot, though, I was able to ditch all that, and the result is
really much cleaner, and safer.

-- 
see shy jo


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .