On Tue, 2025-06-24 at 12:38 -0500, Chris Adams wrote:
> I guess it's a question of which is the bigger burden - taking that same
> package set and just building it directly for i686 (mostly burden on
> infrastructure, some on packagers for build failures or such)

I'd like to highlight that this is a substantial burden. The multilib
code we're carrying around the whole releng chain from koji on up is
ancient, messy and hard to touch. This whole multilib concept is a
*substantial* drag on almost anything you do around release or test.
One of the hardest things to try and reason about in writing my new
rmdepcheck thingy - https://codeberg.org/AdamWill/rmdepcheck - was
"what to do about multilib?" If multilib didn't exist it would've been
*far* less mentally taxing work. And even though my end decision was
"ignore it as far as possible", doing that takes actual work, and
caused two rounds of "why is it giving weird results? oh, multilib
weirdness, I have to Do Stuff about it".

I'm also pretty sure 'dealing with multilib' is a significant reason
why the preliminary phases of compose - pkgset and gather, I forget
which deals with multilib, maybe it's both? - take so long (over an
hour).
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



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