RFE: commit time for rollbacks...

[James Olin Oden <joden malachi lee k12 nc us>]

Hi All,

Presently, the rollback feature of rpm supports settting a time
before which erasures will not occur in a rollback (i.e. via the
%_unsafe_rollbacks macro).  This tackles of the problem of how
do you allow for erasures in a rollback, but also prevent a complete
scrub of the disk by rolling back to time before install.  

One of the developers where I work, suggested  another possible 
safe gaurd that could be put in place.  His idea was to have some
sort of transaction_commit macro that would contain a date beyond
which neither erases or installs could occur in a rollback.  The
idea is that as one upgrades their system they could after running 
various sanity tests commit the current set of rpms on the system
such that they would not be able to be rolled back by setting this
macros date.   Then if anyone wanted to rollback the known good/approved
system they could not, unless they modified this date.

Obviously, being able to set this via the cli would be nice, but like
all things rollback were not quite there yet, and for those of us
using the feature, modifying rpm macro config files has become par 
for the course.  That being said, I was really wanted to see if anyone
found any problem with this policy level feature for rollbacks?  

Cheers...james