Bug#823910: debian-policy: document Build-Depends-Arch/Build-Conflicts-Arch and when it's safe to use them
- To: Johannes Schauer <josch@debian.org>
- Cc: 823910@bugs.debian.org
- Subject: Bug#823910: debian-policy: document Build-Depends-Arch/Build-Conflicts-Arch and when it's safe to use them
- From: Russ Allbery <rra@debian.org>
- Date: Sat, 31 Dec 2016 16:58:41 -0800
- Message-id: <[🔎] 87pok78uke.fsf@hope.eyrie.org>
- Reply-to: Russ Allbery <rra@debian.org>, 823910@bugs.debian.org
- In-reply-to: <147418267095.14255.13902656283430533423@localhost> (Johannes Schauer's message of "Sun, 18 Sep 2016 09:11:10 +0200")
- References: <20160510103159.5806.3075.reportbug@zam581.zam.kfa-juelich.de> <20160713165232.GA13656@xanadu.blop.info> <147418267095.14255.13902656283430533423@localhost>
Johannes Schauer <josch@debian.org> writes:
> Instead, I'd like to make a case for inclusion of Build-Depends-Arch and
> Build-Conflicts-Arch here:
> - the fields add symmetry to the existing Build-Depends-Indep and
> Build-Conflicts-Indep fields
> - the mapping of Build-*-Indep to the build-indep target makes one expect
> there to also be a Build-*-Arch field
> - this mapping also makes the proposed fields logical and well fitted without
> surprised
> - it will avoid installing useless dependencies for architecture dependent
> builds
> - it allows separation of build dependencies needed for build-indep and
> build-arch builds from those that are needed for (for example) the clean
> target
> - it is already supported by much software in the archive, most
> importantly it is supported by package builders and installability
> testers
> Please find attached a patch that documents Build-Depends-Arch and
> Build-Conflicts-Arch.
Thanks, seconded, and this has now been applied for the next upload.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: