> Le mar. 23 juil. 2019 à 08:30, Igor Gnatenko > <ignatenkobrain(a)fedoraproject.org> a écrit : >> * Define new architecture in RPM/libsolv (let's call it "haswell" or >> "x86_64modern") > x86_64avx2 ? or even avx2 ? SOMETHING, though. I can't be the only one here old enough to remember when Linux packages came in .i386, .i486, .i586, and then .i686 flavors. And then gradually the earlier generations were dropped off, and it was all just .i686. (Which some distros merged back into .i386 — a mistake, IMHO — while others kept as .i686.) Doing this split, as much work as it would be on the infrastructure side, would also give us the numbers everyone is clamoring for. We could observe actual download/install rates for both arches, and pull the plug on legacy .x86_64 when the time is right, just as it was done with .i686. Because if something isn't going to run on even some CURRENT x86_64 processors being sold, calling it "x86_64" is just wrong, just like calling Pentium-only packages "i386" was. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
