[Yum-devel] [PATCH] Use state-aware filename rpmdb index if rpm supports it

[James Antill]

On Wed, 2011-08-31 at 21:49 +0300, Panu Matilainen wrote:
> On 08/31/2011 09:20 PM, James Antill wrote:
> > ...another maybe good rule we could do inside yum is to extend
> > protected_multilib so that we only allow:
> >
> > 1. Both foo.i686 and foo.x86_64 installed at once.
> >
> > 2. foo.i686 installed on it's own.
> >
> > 3. foo.x86_64 installed on it's own.
> >
> > 4. foo.i686 can be removed on it's own.
> >
> > ...so if you had foo.i686 installed then you couldn't install foo.x86_64
> > without removing foo.i686 ... and if you had both installed, you
> > couldn't remove just foo.x86_64. Basically just outlawing all the weird
> > edge cases.
> 
> This is very close to what I intend to enforce on rpm side once I figure 
> out how to sanely do it, but the above unnecessarily prohibits some 
> non-problematic cases: installation order does not matter at all,  the 
> only case that really needs to be prevented is removing foo.x86_64 when 
> foo.i686 has 'wrong color' files in it. In effect, when 'wrong color' 
> files are present that package should behave as it dependended on the 
> package /really/ owning that file.

 I agree that installing foo.i686 when foo.x86_64 is already installed,
is 100% fine. Basically just add:

5. foo.i686 can be installed on top of foo.x86_64.

...allowing foo.x86_64 on top of foo.i686 could work, but it seems
significantly more magic and I'd guess it will cause weird problems.
Maybe most importantly, I can't see anyone wanting that (but maybe I'm
wrong there too :).