On Tue, Mar 08, 2022 at 01:55:47PM -0600, Chris Adams wrote: > > Rather than churn 20,000+ packages (plus add a new requirement for every > new package to include an ExcludeArch), why not address this at the > build system? > > Writing a script to generate a list of the buildroot plus multilib > packages, then find all the necessary source packages for those and > their build dependencies, should not be that hard. I don't know how > difficult it would be to then hook that in as a filter to the i686 build > system, hopefully not too difficult? I would think it would be quite a lot of work because it's trying to make koji do something in a way that it's really not currently designed for. If folks are willing to put in the work, I'm sure we would be happy to use it once it's available upstream. > I don't know how the current list of provided multilib packages is > created though. It's created by pungi / python-multilib at compose time using a number of rules and allow and block lists. > I'd probably start with the above script querying all > i686.rpm packages in the x86_64 repo (and working through their source > packages, and those packages' build deps), and if the i686.rpm list is > slimmed down, the above script would trim the deps automatically. > > Then rather than churn almost every package in the distribution, current > and future, fix it in one place. That place can then be updated as > needed. I'm not sure this is going to be at all as easy as that. :( kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
