On Wed, 2007-05-02 at 22:44 -0400, James Bowes wrote:
> James Bowes wrote:
> > I've been working on this as a plugin, as a matter of fact. Right now it
> > sucks for most cases. If anyone is interested in playing with it in its
> > broken state, I can put the git repo online this evening.
> 
> I put a little more work into this tonight, to where it is probably
> useful for some people. The code is at:
> http://git.dangerouslyinc.com/egregious-remove
> 
> For example, 'yum erm serpentine' will pick up a bunch of cd/gstreamer
> related python bindings for removal.
> 
> It still fails for my primary use case, removing kde related programs.
> 'yum erm kdiff3' should pick up both kdelibs and kdnssd-avahi. However,
> it misses both, as kdiff3 depends on kdelibs, kdelibs depends on
> kdnssd-avahi, and kdnssd-avahi depends on kdelibs. Good times.
> 

as we talked about on jabber, we kinda need a transaction database that
includes context information about WHY something occurred to a package.

Ideally we could use it to track all the change to any system using yum.
So we could know that on march 21 foobar was removed by user request and
foobar-lib was removed b/c of a dep on foobar.

It's info that the rpmdb doesn't have and might not have much use for
but we probably should.

It's another good case for per-package pre-and-post-transaction plugin
hooks. Then we could do journalled transactions and also use it as a
nice log for sysadmins for what's happened AND WHY it happened on a
system.

-sv


_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

Reply via email to