On Tue, Jan 14, 2025 at 08:16:15AM -0500, Stephen Smoogen wrote: > On Mon, 13 Jan 2025 at 16:08, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> > wrote: > > > On Mon, Jan 13, 2025 at 12:10:44PM +0100, Jakub Jelinek wrote: > > > 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. > > > > I think this functionality stopped being used ages ago. At least a > > decade, but I think more. So it seems unlikely that it'd work out of the > > box. > > I think there is a gap in communication in this paragraph which may lead to > a lot more confusion. You say that you think the functionality stopped > being used a decade ago, but people have been pointing out that 'it' is > being used in SuSE and other distros. Are we talking about two different > functionalities which have been lost in the pronouns? We are talking about the same functionality, but it also has multiple components that need all to be combined. By "stopped being used a decade ago" I meant "stopped being used in Fedora". It would be great if somebody familiar with how OpenSUSE is doing things summarized here how they are doing it. That said, OpenSUSE is using zypper, not dnf5, and they generally have a lot of their own tooling. So even if rpm supports this, that is far from enough for us to be able to use something like this. (Hypothetically speaking, since I still think that the dynamic approach proposed instead is superior for this particular situation.) Zbyszek -- _______________________________________________ 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
