Bug#530687: Support for architecture wildcards

[Kurt Roeckx <kurt@roeckx.be>]

On Mon, May 31, 2010 at 11:41:15AM -0700, Russ Allbery wrote:
> -	    architectures separated by spaces.	If <tt>any</tt> or
> -	    <tt>all</tt> appear, they must be the entire contents of the
> -	    field. 
[...]
> +	    spaces.  If <tt>all</tt> appears, that value must be the
> +	    entire contents of the field.

Note that it removed the "any" part, and I think that still
applies.

> +	      should not be used for most packages.  Wildcards are not
> +	      expanded into a list of known architectures before comparing
> +	      to the build architecutre.  Instead, the build architecture
> +	      is matched against any wildcards and this package is built
> +	      if any wildcard matches.
> +	    </footnote>

I don't see the point of mentioning this implementation detail?

> +	    If the source package also builds at least one
> +	    architecture-independent package, <tt>all</tt> will also be
> +	    included in the list.
> +	  </p>

This seems to be existing text already, and I think your diff it's
showing everything that was removed.


> @@ -4259,6 +4287,23 @@ Build-Depends: foo [!i386] | bar [!amd64]
>  	  source package section of the control file (which is the
>  	  first section).
>  	</p>
> +        <p>
> +          All fields that specify build-time relationships
> +          (<tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
> +          <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>) may also
> +          be restricted to a certain set of architectures using architecture
> +          wildcards. The syntax for declaring such restrictions is the same as
> +          declaring restrictions using a certain set of architectures without
> +          architecture wildcards.
> +          For example:
> +          <example compact="compact">
> +Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
> +          </example>
> +	  is equivalent to <tt>foo</tt> on architectures using the Linux
> +	  kernel and any cpu, <tt>bar</tt> on architectures using any
> +	  kernel and an i386 cpu, and <tt>baz</tt> on any architecture
> +	  using a kernel other than Linux.
> +        </p>
>        </sect>

Shouldn't that be moved one paragraph up?  And not sure that
repeating that it's about Build-Depends, Build-Depends-Indep is needed.


Kurt