Manoj Srivastava wrote:
+
+ <p>
+ A package may specify an architecture wildcard. Architecture
+ wildcards are in the format <tt><var>os</var></tt>-any and
+ any-<tt><var>cpu</var></tt>. <footnote>Internally, the package
+ system normalizes the GNU triplets and the Debian
+ arches into Debian arch triplets (which are kind of inverted GNU
+ triplets). So when matching two Debian arch triplets, whenever an
+ <var>any</var> is found it matches with anything on the other side,
+ like in:
+ <example>
+ gnu-linux-i386 == gnu-linux-any
+ gnu-kfreebsd-amd64 == any-any-amd64
+ </example>
+ And for example <var>any</var> is normalized to
<var>any-any-any</var>.
+ </footnote>
+ </p>
Do we really need to use the triplets? Do you see some possible cases where we
must really specify the first part?
Does the new dpkg support also the triplets?
Personally I would move it in a footnote, as "future direction".
Now we miss only the "all [linux-any]" like constructs.
ciao
cate
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
