[Yum-devel] Resolving dependencies for postresolve-plugin actions

Paul Nasrat pnasrat at redhat.com
Mon Feb 20 14:31:02 UTC 2006


On Mon, 2006-02-20 at 03:13 -0800, Panu Matilainen wrote:
> Just got reminded of something that has bothered me for a while now by
> getting bitten by it: we should have a second run of resolveDeps() if 
> postresolve-stage plugin changes the transaction set. Otherwise it can 
> leave rpmdb in inconsistent state - for example installonlyn plugin 
> decides to remove old kernels but any kernel-module packages depending on 
> it are still left on the system. Ditto for any other changes in 
> postresolve, not having postresolve actions depsolved limits its usability 
> in various other ways as well.
> 
> Something like this would be needed (just checking for tsInfo size isn't 
> really sufficient but you'll get the idea):

SortedTransactionData uses a changed state on add/remove which we could
put in the parent class.

Paul




More information about the Yum-devel mailing list