On Tue, Jun 24, 2025 at 05:23:24PM +0000, Gary Buhrmaster wrote:
> On Tue, Jun 24, 2025 at 1:45 PM Daniel P. Berrangé <berra...@redhat.com> 
> wrote:
> 
> > If we only want to build a small subset of packages as i686, then
> > rather than doing it as an architecture in koji, IMHO, we could
> > consider doing it as cross-compiled target, creating sub-RPMs
> > from the native x86_64 package, as we do with the mingw packages
> > for example. That could potentially eliminate pretty all of the
> > rel-eng and infrastructure burden, and ensure package maintainer
> > burden is strictly confined to where its needed.
> 
> It is an attractive idea, but can the packages
> do that, and still perform appropriate QA
> and development and debugging (as needed)?
> 
> Cross compile can certainly be used for
> targeted packages, but I am not sure it
> solves the general problem of how big
> the core set of libraries are, and their
> dependencies going all the way down.
> However, I will be quite happy to know
> I am overthinking the potential issues.

Well the set of mingw packages we provide is pretty huge, with many layers
of dependencies down to the base C runtime. Conceptually it isn't difficult
work, just time consuming to get the minimal viable set of packages
working, and a further maint burden. Initally mingw was completely separate
from native, but we ultimately concluded that in most cases it is less
work to have mingw be a sub-RPM of the native package (at the discretion
of the native pkg maintainer to accept or reject). 

IMHO, if people care about the 32-bit Steam use case are willing to invest
the time in creating the cross-built i686 packages, it is an approach to
seriously evaluate.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

-- 
_______________________________________________
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

Reply via email to