OK, so that hasn't changed that much since the last proposal I saw. I don't currently see any way to specify that certain packages are not built in certain profiles, though, which would make cases like this easier (e.g. declare "Built-In-Profiles: !profile:stage1" on the multilib packages instead of what I did with defining excludes flags in debian/rules). -- Daniel Schepler
On Fri, Feb 7, 2014 at 11:42 AM, Sven Joachim <svenj...@gmx.de> wrote: > On 2014-02-07 19:17 +0100, Daniel Schepler wrote: > >> Huh, I wasn't aware that this had finally made its way into dpkg. So >> yes, that does make sense. >> >> Is there any way to specify the corresponding changes in Build-Depends >> yet? > > Yes, use <!profile.stage1> in anything you don't need for a stage1 build. > See https://blog.mister-muffin.de/2014/02/06/botch-updates/ and > deb-src-control(5). > >> Although, depending on how it works, even if it's in dpkg we >> might not be able to actually use it in real uploads until jessie+1. > > It certainly won't be allowed in the archive before jessie is stable. > Also apt, sbuild and pbuilder don't currently understand this syntax. > > Cheers, > Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
