On Mon, Jan 13, 2025 at 09:11:35AM +0000, Zbigniew Jędrzejewski-Szmek wrote: > First, this would require setting up the infrastructure to build and > store and distribute multiple builds of a single version of a > package. This is something that Fedora currently doesn't do, so it'd > require changes to operations in mock, koji, bodhi, the CI, mirrors. We've been building packages like that for years, so I don't understand how it would require changes. E.g. we had glibc.i386 and glibc.i686, when glibc was built, it was built for both of those architectures and rpm/yum chose the right one. > Second, dnf would need to learn about this and install the appropriate > variant. I think it should have that support like it had for i686 vs. i386. > Third, this choice would be "permanent", i.e. it would be done once at > package installation time. If the user tries to boot the same image > on different hardware, it might fail. This is inferior to the proposed > approach where the choice is made at runtime. It is superior to that, because you don't have to pay the cost every time you run the program. Jakub -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
