On Wed, Mar 5, 2008 at 11:52 AM, seth vidal <[EMAIL PROTECTED]> wrote: > > On Wed, 2008-03-05 at 16:40 +0200, Panu Matilainen wrote: > > > Indeed. The thing here is that if you limit the rollback scope to just > > config files, things suddenly become far more manageable. It wouldn't cost > > an arm and a leg to (optionally) store the entire config file history > > separately, say, in a real SCM or something resembling one. > > > > Imagine being able to diff the config files between this and the previous > > (or a year ago) version, or what's currently on the system vs what the > > package contained when originally installed. Etc. > > > > I'd guess that quite a few sysadmins would just love that... > > This might be off-subject for this list but maybe a plugin for yum that > did: > > pre trans: > for pkg in transaction: > if the pkg is an update, > grab up the current config files and check them into an scm > do the transaction > post trans: > for pkg in transaction: > check the new versions (if any) into the scm > > you could even use yum's new packageobject.verify() code to make it all > spiffy and easy to look for changes. I think that would be very nice. The hard part is dealing with multiple SCM's, but thats not so hard really...just a little driver layer.
...james _______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org https://lists.rpm.org/mailman/listinfo/rpm-maint
