On Fri, 2007-02-16 at 01:06 -0500, Seth Vidal wrote: > Update of /home/groups/yum/cvs/yum/yum > In directory login1.linux.duke.edu:/tmp/cvs-serv18850/yum > > Modified Files: > constants.py depsolve.py transactioninfo.py > Log Message: > > all of this may need to be rolled back but: > > - add an 'updated' txmbr for tsInfo so we can easily see what's being > removed, implicitly as part of an update > - make _checkUpdate() in YumDepsolver be an amalgam of install and remove > - add the TS_UPDATED constant to constants >
I commented out a big chunk of code in order to play with it some. The interesting bits: 1. this appears to work for the update cases I could test against 2. it might be doing the right thing but I'm not positive I'm certain it is not an attractive or final implementation. If we find that this works I'd prefer to not have to use the grotty mechanism of grabbing the related po and searching for it in the tsInfo. Ideally, we'd just store related txmbr's in each txmbr so we could easily look them up and pass them around. Additionally, if we get this working would it make sense to move tsCheck() into tsInfo and pass in some of our other pieces, if only b/c it seems like a more appropriate place to store that method? -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
