Hi Christof, On Mon, May 23, 2005 at 09:55:05AM +0200, Christof Pintaske wrote: > Christian Lohmaier wrote: > >Christof Pintaske wrote: > [Patches & RPM] > >What is wrong with the symlink-approach? > [symlink-approach] > >The only drawbacks I see are: > >* requires --replacefiles to install > > no need for replacefiles, you only update the symlinks and install a new > file.
Let me see what process I was thinking of.. :-) > >* loose the ability to verify the package/need for a custom > > %verify-Script > > sorry, I don't understand that. The package database integrity will be > fully maintained with the symlink approach without any --forceXXXX or alike. Hmm - not sure what I meant... You're right - with symlinks and having the patch-package install new files you don't require --replacepackages and a custom verify-script/declarations, but you end up in having the old files lying around... Not being a friend of that I probably thought: Well, then just replace the original one (from the other package, thus --replacefiles). But using this method you don't need the symlinks at all (I'm still not sure what my thinking was..) Sorry for the confusion. So to sum up again (please add your pros/cons to that list esp. to the patch-rpm method since I don't know that myself): Symlink-method: Cons: * leaves the old files on the harddisk (could be removed by the patch and the original package could specify "missingok") * needs a postinstall-script to update the symlink * may need some work in OOo to make it work with symlinked components Pros: * no command-line parameter to force the installation necessary * can tell whether a patch is installed by doing a ls /path/to/OOo * package can be uninstalled w/o problems (when original file is not removed) "just-replace-the-file"-method: Cons: * needs command-line parameter to install (overwrites file from othe package) * possibility to verify the package is limited/custom verify scripts (that tells the user that he shoud check whether a patch-rpm contains the file that fails verification) should be created * need to query the rpm-database to check whether a patch is installed * when uninstalling you need to reinstall the files replaced by the patch Pros: * no change to the components (make them work with symlinks) necessary * no old files lying around Patch-rpm-method: Cons: * currently only available for SuSE * even when adapted to "official" RPM packages still would not be compatible with older versions of RPM Pros: * "non-hack" solution (expect from the hack to RPM itself :-) ciao Christian -- NP: Metallica - Turn The Page --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
