I think it would be Build-Depends: ..., python-all <!profile.stage1>, ...
But we can't upload packages with the new Build-Depends syntax until at least after the next release as it's not backwards compatible with stable's toolchain. -- Daniel Schepler On Wed, Mar 5, 2014 at 3:47 PM, Christoph Biedl <debian.a...@manchmal.in-ulm.de> wrote: > Daniel Schepler wrote... > >> Here's an updated version of my patch, with some of Eleanor's patch merged >> in. >> It also updates to use DEB_BUILD_PROFILES which recently landed in dpkg, and >> the Build-Profiles field support which just a couple days ago made it into >> debhelper (hence the bump in the debhelper Build-Depends version). > > Looking closer ... are there documents that give an idea which binary > packages can be excluded safely? More precisely, is the libmagic-dev > package needed for stage1? I'm not sure at all. Additionally, I guess > we should exclude the python packages from the build dependencies, > i.e. > > Build-Depends: debhelper (>= 9.20140227~), > autotools-dev, > python-all <!stage1>, > python3-all <!stage1>, > zlib1g-dev, > > Or <!cross !stage1>? > > Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
