On Thu, Feb 12, 2009, Nicolas Thierry-Mieg wrote:
>
>
>Kai Schaetzl wrote:
>> Ian Forde wrote on Wed, 11 Feb 2009 20:01:21 -0800:
>>
>>> locate rpmsave
>>> locate rpmnew
>>
>> rpmsave is left from *un*installations, rpmnew is the *new* file, there is
>> no file overwritten. rpm usually doesn't overwrite files if they got
>> changed.
>
>AFAIK this is not correct, a package upgrade can create either of these
>(or both, or neither of them despite your having edited a file). And
>that's the way it should be, either choice can be justified.
>It depends on the package's SPEC file. rpm just does what it's told,
>everything is in the hands of the package maintainer.
I think that the only time a .rpmnew file is created is if the
SPEC file specifies ``%config(noreplace)'' for a file. If the
``noreplace'' option is not used, the .rpmsave files are created
either when a package is removed, or when a file specified as a
configuration file in the RPM SPEC file is updated and the file
is sufficiently different from the default (for some definition
of suffieiently).
In the OpenPKG portable packaging system, which is RPM based, the
presence of any .rpmnew or .rpmsave configuration files will
prevent a package from starting, and warning messages will be
generated until the situation is resolved.
Bill
--
INTERNET: bill@xxxxxxxxxxxxx Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
Voice: (206) 236-1676 Mercer Island, WA 98040-0820
Fax: (206) 232-9186
The obscure we see eventually, the completely apparent takes longer.
-- Edward R. Morrow
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
