[Yum-devel] [PATCH] - add historyend and historybegin plugin conduits - add history write_addon_data and an addon_data path so we can write out arbitrary data to a file stored per history file and per transaction id - add historypluginconduit which gives the user access to yumbase.history directly

[seth vidal]

On Tue, 2010-06-22 at 16:26 -0400, James Antill wrote:
> On Tue, 2010-06-22 at 15:56 -0400, seth vidal wrote:
> > On Tue, 2010-06-22 at 00:58 -0400, James Antill wrote:
> > > > -
> > > > +            self.plugins.run('historybegin')
> > > >          #  Just before we update the transaction, update what we think the
> > > >          # rpmdb will look like. This needs to be done before the run, so that if
> > > >          # "something" happens and the rpmdb is different from what we think it
> > > 
> > >  I'd guess plugins would want to know the rpmdbv? Maybe not.
> > 
> > I'm not sure the context - but who knows - I guess the use case I was
> > thinking of was storing additional info on what's gone on in the
> > transaction or any dump of data out of one of our other resources. So
> > knowing the rpmdbv to go into the additional history seems less
> > important, you'll know the rpmdbv it's associated with b/c the history
> > db knows the rpmdbv and each additional_info is linked to the tid.
> 
>  Yeh, I think the use case I was thinking about was "caching stuff" and
> that needs another plugin hook ... as you want to know the rpmdbv and
> the calculated future_rpmdbv, and you want to know it when history is
> disabled. So ignore this.


'caching stuff'?

What kind of caching could you do of history information?

-sv