[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#575760: Bug#575761: Bug#575760: x86 architecture names are confusing



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Le 08/01/2011 06:23, Gerfried Fuchs a écrit :
> 	Hi!

Hi,

> * Osamu Aoki <osamu@debian.org> [2011-01-04 14:21:14 CET]:
>> This needs to be changed and reordered to:

[...]

>> This order is the current popcon data order:
>> http://popcon.debian.org/
>> So we will not ask user to look through long list.
> 
>  Erm, the ordering of the hash doesn't gain you anything. Actually
> hashes in perl are unsorted by definition, it's explicitly undefined in
> which order the keys will be returned.
> 
>  If you want to fix the sorting that will have to be at the point where
> it's used, not in the hash definition.

I just took care of this part: the hash is now shared among releases
(and there name are now translatable) in english/releases/arches.data
and the choice of valid architectures and ordering is made via a table
in english/releases/&releasename;/release.data (I ordered the Squeeze
ones using popcorn data, and kept the alphabetic order of architectures
codename for others, it may worth to take care of ordering at least
Lenny's architectures using popcorn if nobody objects).

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJNKORoAAoJELgqIXr9/gnyBtUP/R/txHieBH5KrGRlEs9kDiTw
h2l8YpmCzytHy9QiDRtbAMflk2Dqc1dlMQR1NrDkQWWj9FyPfMFREmhoYU9hIueg
RwWyKLj1bPSxsipJNXvcxd6FXx3aybl1FCS6mPXTUeGxEJEgSxjxva6K69eebPFq
LDEBtSHsY0ks+MghVxDN1/2vr916iz7h3FU8B3qaG2N7TTvmwcICZVovy5XgNf3v
T688oTU6xKq3pCmAmVKY8OMi16WL6/Neue0C9GwYketUrOT4joMEbFCcHfsPcV9+
Jf5/G2nMn0VN43c4FbUlHJXh1qgcq9oZFkGIB/0Fv8y1gMeOBfShInURaA2MNDsG
xJLc5wndA1wTXw++XL8brzWz6SVDA5PuSkdD2NtR4pAX5xrvyOOlpor+u7/zG9bl
Ui3DcODsYyApX8ibqlewarcVweBZUmLsU80iDn9mGVQjt0guTC3h5l4aUUR7asS7
+8IdYvGFb/JXn01Qd4GNFdSRX0kDb3XvwhcF83Yrjh2JNRvujUuTiLnC6hsMyPK5
stXB3ZV2QBek6HdeVimDCk92LNo50jFDTFWBZG6fLewBY7zxwvQUTdhM3lLmDgDx
x5NJFisLmLfYw5XLVvHSXwPnUNjTFImz/vPm1RMwxn1zruCLkRt4FfHSCRNrwACM
CmGGK7x+/gkjVJlREW/3
=nK1h
-----END PGP SIGNATURE-----



Reply to: