* Daniel P. Berrangé: > What kind of "potential issues" are liable to justify reversing > the decision to drop i386 ? > > Assuming we confirm that the Wine change is just a formality at > before approving this change, that would address the big blocker > in Fedora. > > What else would be high profile enough *in Fedora* to merit a > blocker ? IMHO external apps should not influence our decision, > and must adapt to what the distro decides to provide. > > > The QEMU release coming in Dec this year is expected to be > dropping all support for building on 32-bit hosts, and the > ripple effect on packages across Fedora is non-negligible.
NodeJS is in a similar boat, apparently (see the thread “Dropping i686 from NodeJS build architectures”). Both situations could in theory be solved by having 64-bit binaries in the 32-bit buildroot. The x86_64 build could copy the already-built binaries into a specially-named noarch subpackage, and the i686 build would just build stub packages that depend on the noarch packages. We can do this for glibc as well (like we already do in the opposite direction, via the glibc32 package), so you wouldn't even have to link statically. And if we do it for binutils and gcc, quite a lot of i686 build failures due to its limited address space would just go away. However, this is not really forward-looking work. While technically interesting to some degree, the effort required would likely be spent in a more impactful way somewhere else. I think it's quite likely that soon (maybe in a way) we encounter more issues that make the i686 port even more challenging. (Funny thought: In a way, the whole discussion is a testament of the portability of Fedora and our build approach.) Thanks, Florian -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
