[Yum] [PATCH] avoid installing 2 copies of everything multilib

seth vidal skvidal at phy.duke.edu
Tue Aug 23 02:07:22 UTC 2005


On Mon, 2005-08-22 at 22:05 -0400, seth vidal wrote:
> On Mon, 2005-08-22 at 21:56 -0400, Christopher Allen Wing wrote:
> > The default behavior of yum when doing an install on a biarch system is to 
> > install both packages (the main arch and the compatibility arch), e.g. 
> > running 'yum install libfoo' will install both:
> > 
> >  	libfoo.i386
> >  	libfoo.x86_64
> > 
> > 
> > This is annoying and contrary to, e.g. the way the Red Hat installer 
> > works.
> 
> Not for loooooooooong. :)
> 
> > This doesn't affect upgrades; when 2 arches of the same package are 
> > installed, both will be upgraded as usual. It also doesn't prevent a i386 
> > package from being installed, for instance, if no x86_64 package by that 
> > name exists. It also doesn't change dependency resolution, so if the i386 
> > package is actually required by something else, it will still be 
> > installed.
> 
> And it completely runs contrary to:
> 
> yum install foo*
> 
> 
> b/c now it won't install foo* that _can_ be installed.
> 
> it will only install foo* of the multilib arch.
> 
> not exactly obvious behavior is it?

I've also never figured out what was so heinous about having both i386
and x86_64 of a package installed by default. what's the bad thing that
happens? If you're really that hellbent for leather to avoid the i386
pkgs why not add an exclude at the top of your yum.conf?

exclude=*.i386 *.i686 *.i586 *.athlon

-sv





More information about the Yum mailing list