Christian Lohmaier wrote:
Christof Pintaske wrote:
we are aware of the SuSE patching mechanism for RPMs, and indeed it
seems to provide all the functionality we need.
Even if it got adapted, there still would be many systems that do not
use the patch.
that's true, but it holds true for all technical progress. So it would
be still better to start and have a solution in future.
What is wrong with the symlink-approach?
The symlink approach is truly ingenious :-) However you still end up
with having the old file residing on your disk without having any proper
use for it. And it's not a generic approach working out of the box for
all files.
The only drawbacks I see are:
* requires --replacefiles to install
no need for replacefiles, you only update the symlinks and install a new
file.
* 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.
best regards
Christof
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
