Bug#163666: debian-policy: Unclear result with [arch] and |
- To: 163666@bugs.debian.org
- Subject: Bug#163666: debian-policy: Unclear result with [arch] and |
- From: Russ Allbery <rra@debian.org>
- Date: Sun, 01 Feb 2009 10:10:57 -0800
- Message-id: <[🔎] 87tz7edo3y.fsf@windlord.stanford.edu>
- Reply-to: Russ Allbery <rra@debian.org>, 163666@bugs.debian.org
- In-reply-to: <20090126180302.GV4175@volo.donarmstrong.com> (Don Armstrong's message of "Mon\, 26 Jan 2009 10\:03\:02 -0800")
- References: <E17yYzI-0004P6-00@localhost> <873cqtyvck.fsf@glaurung.green-gryphon.com> <20021029142940.GA308@uvt407-5.ruk.cuni.cz> <87prprub3n.fsf@windlord.stanford.edu> <20080706043559.GA26108@zulo.hadrons.org> <87skn7j7ml.fsf@windlord.stanford.edu> <20090126180302.GV4175@volo.donarmstrong.com>
Don Armstrong <don@debian.org> writes:
> On Sun, 25 Jan 2009, Russ Allbery wrote:
>> + If the architecture-restricted dependency is part of a set of
>> + alternatives using <tt>|</tt>, that branch of the alternative is
>> + ignored completely on architectures that do not match the
>> + restriction. For example:
>> + <example compact="compact">
>> +Build-Depends: foo [!i386] | bar [!amd64]
>> + </example>
>> + is equivalent to <tt>bar</tt> on the i386 architecture, to
>> + <tt>foo</tt> on the amd64 architecture, and to <tt>foo |
>> + bar</tt> on all other architectures.
>
> The "branch" part is slightly confusing; I think you want "that
> alternative". [Otherwise it makes it sound like foo [!i386] | bar
> [!amd64] should be treated like foo on everything not i386 or bar on
> everything not i386/amd64; you have to read the example to figure out
> exactly what is meant.]
Good call. Updated.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: