Architecture in .dsc may now be "any all"

With dpkg >= 1.16.1, the value of the Architecture field in the .dsc
is generated a bit differently.

The goal is to be able to always know when a source package generates an
architecture-independent package. Currently as soon as one binary is
"Architecture: any", the value generated is "any" and we have no way to
know that there are "Architecture: all".

With dpkg >= 1.16.1, the "all" is kept even if there's a binary package
with "any". So the resulting value is then "any all". This allows
wanna-build to know if it must schedule a build for the "Architecure: all"
packages.

diff --git a/policy.sgml b/policy.sgml
index 9b4a93e958c6f87a7615698db42dbc5686db2cad..0650306fec093eb14b94337818ad4d936b679eb0 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -2975,10 +2975,14 @@ Package: libc6
 
          <p>
            In the source package control file <file>.dsc</file>, this
-           field may contain either the architecture
-           wildcard <tt>any</tt> or a list of architectures and
-           architecture wildcards separated by spaces. If a list is
-           given, it may include (or consist solely of) the special
+           field contains a list of architectures and architecture
+           wildcards separated by spaces. When the list contains the
+           architecture wildcard <tt>any</tt>, the only other value
+           allowed in the list is <tt>all</tt>.
+         </p>
+
+         <p>
+           The list may include (or consist solely of) the special
            value <tt>all</tt>.  In other words, in <file>.dsc</file>
            files unlike the <file>debian/control</file>, <tt>all</tt> may
            occur in combination with specific architectures.
@@ -2989,19 +2993,23 @@ Package: libc6
          </p>
 
          <p>
-           Specifying <tt>any</tt> indicates that the source package
+           Specifying only <tt>any</tt> indicates that the source package
            isn't dependent on any particular architecture and should
            compile fine on any one. The produced binary package(s)
-           will either be specific to whatever the current build
-           architecture is or will be architecture-independent.
+           will be specific to whatever the current build architecture is.
          </p>
 
          <p>
            Specifying only <tt>all</tt> indicates that the source package
-           will only build architecture-independent packages.  If this is
-           the case, <tt>all</tt> must be used rather than <tt>any</tt>;
-           <tt>any</tt> implies that the source package will build at
-           least one architecture-dependent package.
+           will only build architecture-independent packages.
+         </p>
+
+         <p>
+           Specifying <tt>any all</tt> indicates that the source package
+           isn't dependent on any particular architecture. The set of
+           produced binary packages will include at least one
+           architecture-dependant package and one architecture-independent
+           package.
          </p>
 
          <p>
@@ -11272,4 +11280,4 @@ END-INFO-DIR-ENTRY
 <!-- Local variables: -->
 <!-- indent-tabs-mode: t -->
 <!-- End: -->
-<!-- vim:set ai et sts=2 sw=2 tw=76: -->
+<!-- vim:set ai sts=2 sw=2 tw=76: -->