Re: Handling multilib

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

 



On Tue, 2007-03-20 at 11:02 -0400, Bill Nottingham wrote:
> So, the idea I had is that for things like this:
> 
> - you subscribe your multi-arch system to both channels
> 
> - the decision for what is installed is done via yum
> plugins/configurable
>   yum behavior
>   
> You could say 'multlib=devel', to get development packages and their
> dependencies. Or 'runtime', to get runtime libraries. Or 'none', to
> get, well, nothing.

That makes a certain amount of sense. Although I don't really think we
need to offer the "runtime" option -- what's the point in a bunch of
libraries which never get used? Just pull them in if they're required,
surely -- either by a -devel package or by an executable? Let the
default be 'none', which gives you nothing but the special cases like
gdb and strace.

-- 
dwmw2

--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers

--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly

[Index of Archives]     [Fedora Users]     [Fedora Development]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux