Bug#530687: debian-policy: Please provide policy for architecture wildcards

[Andres Mejia <mcitadel@gmail.com>]

On Wednesday 27 May 2009 07:49:09 Julien Cristau wrote:
> On Wed, May 27, 2009 at 07:30:57 -0400, Andres Mejia wrote:
> > On Wednesday 27 May 2009 06:51:58 Julien Cristau wrote:
> > > This makes it sound like you can't mix architecture names and
> > > architecture wildcards.  Is that on purpose?
> >
> > Current policy has this wording and I didn't want to change that, so
> > yes, it's on purpose.
>
> Not quite.  Current policy says "arch list or 'any' or 'all'" and that's
> fine (at least for debian/control), because it wouldn't make sense for a
> binary package's Architecture field to be 'any' or 'all' *plus* an
> explicit list of architectures.
> (yes, .dsc might need different rules, but.)

Ok, here's the wording current policy.
"one may specify a list of architectures separated by spaces, or the special 
values any or all."

Here's part of my proposal.
one may specify a list of architectures separated by spaces, a list of 
architecture wildcards separated by spaces, or the special values any or all.

What I'm trying to say is "arch list or arch wildcards or 'any' or 'all'", and 
judging by how current policy is written, I assume 'or' to mean inclusive OR, 
not XOR.

> > My assumption is that however wrote this part of policy meant 'or' to be
> > inclusive, not exclusive.
>
> Please reconsider your assumption :)

Wrote that wrong. 's/however/whoever'.

-- 
Regards,
Andres