Re: .rpmsave vs .rpmnew

[Alan Eldridge <alane geeksrus net>]

>> >> So I have a config file I have changed. I install the new rpm. My config
>> >> file gets renamed to .rpmsave. My configuration is no longer in place. This
>> >> contradicts the behavior you described.
>> >>
>> >> The file is marked (noreplace).
>> >
>> >its only marked noreplace in the rpm you've just installed, not the one
>> >that is already in the db.
>> >
>> 
>> File is marked noreplace in both rpms. (Extreme case: they're the same rpm.)
>> Still, existing file is moved to .rpmsave.
>> 
>
>*Why* do you want a file to be installed with extension .rpmnew?
>
>You can always just put the extension on the file in package.

I don't want the existing conf renamed. The existing conf should still work
after installation without manual intervention to rename a file back.  I
want "noreplace" to really mean exactly that.

-- 
Alan Eldridge
from std_disclaimer import *