Le ven. 22 mai 2026 à 14:20, Chris Adams via rpmfusion-developers <[email protected]> a écrit : > > Once upon a time, Simone Caronni <[email protected]> said: > > However, this package contains a tarball, which, despite its name (we're > > going into Windows' System32 territory here...) contains binaries for all > > the architectures the client supports. > > Can this tarball not be split up? It makes no sense to ship x86_64 > binaries to aarch64 clients (or vice versa). Well, that's an un-important optimization. (at least in the rpmfusion-nonfree section where we can have pre-built binaries). Simone mentioned FEX that allows to run x64 binaries in aarch64 host environnement. and having both target x64/aarch64 bootstrap binaries here will help no matter of the host userspace architecture. FEX is using a dedicated fedora image to provide aarch64 for some basic x86_64 libraries. (I don't know if that bundles i686 libraries).
But the issue is that noarch stands for no specific architecture dependencies. RPM doesn't have a concept for "all/fat arches" packages. So my point is that having the package arched is a better approximation than having it noarch given that we still need to describe specific arched dependencies. In Fedora (and RPM Fusion), noarch packages are exactly the same across all arched repositories so if they become different, this --will-- break hard at build time. There is no way around. _______________________________________________ rpmfusion-developers mailing list -- [email protected] To unsubscribe send an email to [email protected]
