[Yum-devel] ideas that have come up in the last couple of days

[Neal Becker]

On Saturday 01 March 2008, seth vidal wrote:
> On Sat, 2008-03-01 at 08:25 -0500, Neal Becker wrote:
> > On Saturday 01 March 2008, seth vidal wrote:
> > > On Sat, 2008-03-01 at 08:14 -0500, Neal Becker wrote:
> > > > I had advocated for cleaning each package right after installing,
> > > > which at the time seemed to get positive responses.  This is what
> > > > smart does. My motivation is from one experience where a big update
> > > > got aborted, leaving a mess.
> > >
> > > Changing the ordering is not such a good idea. If we want to rearrange
> > > the transaction ordering I'd rather we do it in rpm.
> >
> > Could you elaborate?  What problems do you see?
>
> /sbin/ldconfig issues
>
> scriptlet ordering issues
>
> removing the packages immediately after installing the new ones doesn't
> guarantee that your system is in a usable state afterward. So you're in
> the same boat as far as an aborted transaction.
>
> It's perfectly possible it will work fine. Though I'm curious if the rpm
> devels have a good reason for the ordering as it is now. I seem to
> recall that rpm used to do ordering like that and switched away from it
> to how it is now.
>
> Writing our own ordering is do-able - just not sure it is worth the time
> it'll take to do it and then make sure it is correct/valid.
>
> -sv

IIRC, the issue I ran into was that if yum aborted, you were left with 
multiple versions of packages installed.

Perhaps there is another way to handle this?  Sounds like the same sort of 
technology used in database, or journal file systems.