Bill Nottingham wrote:
> The issue there is then you have to properly determine what packages
> to remove from the repo (unless you just keep everything, which has its
> own problems); in this case, recomputing actually makes the code simpler.
Sure, it makes the code simpler, but a lot slower! Often, performance
optimizations require more complex code.
> While that would make things simpler and shorter, I doubt it's really
> practical. Enough people use and want multilib that I don't think we can
> just unilaterally remove it. Moreover, the multilib portion of the compose
> isn't the primary time eater.
>
> I certianly don't want to go back to the whitelist case where every time
> someone needed a new multilib package we had to update a static whitelist
> in the update push tool. That's just silly.
Why can't we just tell them to add the 32-bit repo to their configuration?
Possibly even ship fedora-32bit and fedora-updates-32bit configs (disabled
by default)? With the exactarch=1 setting (the current default), this
shouldn't be a big problem. The only problem I see is that people would run
into file conflicts if they use exactarch=0 or yum install
someapplication.i686, but it's easy to close those as NOTABUG ("sorry,
multilib is not supported for this package, just use the 64-bit version").
If those reports become a big problem, isa-based Conflicts tags could be
added.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
