Russ Allbery wrote:
"Giacomo A. Catenazzi" <cate@debian.org> writes:Do we really need to use the triplets? Do you see some possible cases where we must really specify the first part?Isn't someone working on a klibc port? That would require using the triplet.
Does the new dpkg support also the triplets?Personally I would move it in a footnote, as "future direction".If dpkg already supports it, it certainly shouldn't be a future direction.
ok. fair enough. BUT: the original proposal and this proposal contain only the duet: + 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 The triplets are listed only in the footnote (which is IMHO confusing). But if we want to support the klibc (and in general different libc ABI), as it seems nice, this proposal should be more explicit about the use of triplet, allow them in the usual places, and policy should set the default value. ciao cate