puplet/pup/yum-updatesd... rethinking the mechanism

[Bret McMillan]

On Fri, Jun 16, 2006 at 08:12:42PM -0400, Bill Nottingham wrote:
> seth vidal (skvidal at linux.duke.edu) said: 
> > On Fri, 2006-06-16 at 17:23 -0400, Bill Nottingham wrote:
> > > Jeremy Katz (katzj at redhat.com) said: 
> > > > > Still, why does it need computed again?
> > > > 
> > > > What if something has changed since the last time the daemon ran?  There
> > > > are cases which could end up installing/updating packages which you had
> > > > since done a removal around.  And in any case, as long as the interface
> > > > is doing the updating, you have to have done all the hard stuff around
> > > > finding "what are the updates"
> > > 
> > > But, if nothing has changed, why would it need to recompute dependencies (which
> > > it currently does...)
> > 
> > how do we know if nothing has changed? Are we going to take a checksum
> > of the rpmdb?
> 
> Heh. I suppose you could keep a timestamp, or the log of the last rpm transaction.
> Being able to do this simply would actually be a reason to have the code daemon-side.

We do that in RHN... /usr/share/rhn/actions/packages.py, grep for
checkNeedUpdate.  I think veillard added this some time ago, but I
could be mistaken.

--Bret