Re: F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 8, 2022 at 9:11 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
>

(...)

> How many examples of things like Wine & Steam do we actually have ?
> I feel it must be a pretty small list of things which are important
> to a large number of users and yet need 32-bit.
>
> If we only consider Wine & Steam, we can make a clear list of
> exactly what small set of 32-bit libs are needed, we can declare
> everything obsolete. We could start by simply excluding all those
> unneeded RPM from the compose, and then let maintainers disable
> it in their RPM builds without fear of causing deps problem.

I have considered an approach like this. But as always, it's just not
that simple.

One of the most problematic things are transitive BuildRequires:
Even if you know you need to keep libfoo.i686 and libbar.i686, how do
you determine the transitive dependencies that are needed to keep
those packages around?
And by that, I don't only mean Requires, but also transitive
BuildRequires, i.e. if libfoo BuildRequires foolangc, which
BuildRequires some other stuff, etc, all of which still needs to be
there, or at some point, libfoo.i686 will either fail to build or fail
to install.

I have thought about this issue for months before submitting this
Change proposal, and it's the best I think we can do without breaking
tons of stuff or requiring massive amounts of work from the Change
owner (me). At this point, I do think that a safe and officially
encouraged opt-out mechanism for individual package maintainers is the
only way we can do this *safely* at all.

Of course, dropping i686 entirely will come eventually, but I don't
think we can do that just yet. Too much 32-bit x86 software is still
around.

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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux