Hi, On Wed, 25 Jan 2012, Don Armstrong wrote: > On Thu, 26 Jan 2012, Guillem Jover wrote: > > I implemented this, but then realized that it cannot be done > > cleanly, as dpkg-deb is called from inside debian/rules and will > > always place the binary packages under «..», so dpkg-buildpackage > > would need to move the files itself afterwards. While that could be > > done, it might not avoid the problem you refer to. > > Hrm; true. I actually wanted this primarily for debuild -S, but > solving it for everything is probably necessary to solve it at all.
Note that dpkg-source also creates files in the current directory and expect to find files in the current directory (and dpkg-buildpackage changes the current directory to ".." for the needs of dpkg-source). So if you change the current directory to your output directory, you also have to do something to ensure that dpkg-source keeps on finding the orig tarballs. > The hack of sending an env option through to dpkg-deb is all kinds of > ugly... Why would it be more ugly than dpkg-buildpackage -j setting DEB_BUILD_OPTIONS="parallel"? Of course, if there would be no constraints, I would not pick up an env variable as preferred way to pass options but there are many tools who are accepting options through the environment (think GZIP, TAR_OPTIONS, etc.). I don't see why we couldn't do that. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
