reopen 162348 thanks On Sun, 2006-07-09 at 11:30:02 +0200, Nicolas François wrote: > Version: 1.13.18
> On Thu, Sep 26, 2002 at 12:36:54AM +0200, Henning Spruth wrote: > > I'm trying to use dpkg to build and package software for the VR3 Linux PDA. > > To > > do so, I need to install the package on the host relative to some base > > directory, I also need to keep the package admin data for these PDA files > > separate. > > 2. dpkg-buildpackage doesn't allow to specify the admin directory, which is > > required for dpkg-parsechangelog and dpkg-checkbuilddeps > > dpkg-parsechangelog do not uses the admin directory (/var/lib/dpkg), but > the library directory (/usr/lib/dpkg). > > For dpkg-checkbuilddeps, see below. > > > 3. dpkg-checkbuilddeps does't have a switch to specify the admin directory > > Also, I don't think dpkg-checkbuilddeps should check the dependencies > regarding a non standard admin directory (the programs need to be > installed in the host building the package, not on the target host) I agree it should not check the dependencies there by default, but the admin should be free to change this kind of stuff, in the same way that is allowed with the other commands. > Hence, I'm closing this bug. I'm reopening the bug, and will commit now the few changes that will fix this. > To build a package for another target, I recommend a chroot, or dpkg-cross. That's a fine preference, but sometimes you may want to avoid having to run commands inside a chroot. And about dpkg-cross, I think its functionality should be merged back into dpkg. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
