[Yum-devel] transaction checking

[Menno Smits]

seth vidal wrote:
> Alexandre Olivia pinged me with a request and it kinda emerged out as
> this idea:
> 
> 1. write out a 'what we're going to do' list pre-transaction
> 2. delete entries from the last as we complete each step
> 3. if we complete the whole transaction, delete the file.
> 4. if we don't complete the transaction offer a way to finish the
> transaction to the user.
> 
> Now this would require that we break down an update in 'install' and
> 'erase' sections for the file listing, but it's not terribly difficult.
> 
> What do y'all think? I was actually thinking of tying this into the
> history concept that Terje was talking about before.

Just thinking of the top of my head here... could the transaction state 
be saved by writing out pickled TransactionData objects at each step of 
the transaction? This of course requires that TransactionData is updated 
as the transaction progresses which I haven't checked.

Just a thought.

Menno