On Mon, 2003-03-17 at 17:13, Wesley J Landaker wrote: > On Monday 17 March 2003 5:35 pm, Pascal wrote: > > # urpmsave --dir ~/rpmsavedir myrpmname > > (before updating glibc and crashing all the system :) ) > > creates a tgz of all files installed by the rpm in the specify > > directory so that u can restore them in case of emergency > > This would be handy if it would have options for restoring backed up > rpms made in this fashion and handled doing smart things with the urpm > database.
Are you talking about a form of something like a rollback.. meaning if you do something... it karks your system you can "rollback" to a known good state and try again? > > A simple implementation isn't too hard, though: > > #!/bin/sh > rpm -ql myrpmname | xargs tar cvfj ~/rpmsavedir/myrpmname.tar.bz2 > > > and/or better what we use on IBM AIX 'installp' package manager: > > > > # urpmi --apply myrpm > > (which will save replaced files to some urpmi specific save directory > > and apply the new myrpm version to the system) > > > > # urpmi --commit myrpm > > (which will commit the apply, ie remove the saved files from the > > apply, once the new version is sufficiently tested) > > > > # urpmi --reject myrpm_qualified_name_and_version > > (which will uninstall files from the version applied specified and > > restore files from the previous version saved from the corresponding > > apply) > > I like this part--especially for upgrading when you're not *quite* sure > if it's going to work. ;)
