Brian J. Murrell wrote:
> As reported here a while ago, rpm is creating *.rpmnew files for any
> config file that exists, whether it was modified since package
> installation or not.
>
> This is *really* ugly. It means that a config file for a given
> package that has not been modified will *never* be updated to the new
> version of the default file when a package is upgraded. It is
> inevitable that this is going to cause breakage as newer config files
> don't get installed with newer versions of a package.
>
> Thots?
>
> b.
I think that RPM creates a ".rpmnew" file when "%config(noreplace)" is
set before the file name in the spec file. This is good when you
customized a configuration file and would not like to see it replaced by
a newer default config file. As long as the program does not change the
way it stores information in the config file, that will not break
anything, otherwise, it should be written in the Release Notes of the
new version, and the packager removes the "(noreplace)". Then you will
get a "rpmsave" file.
About the fact that the rpmnew file is created even if it is the same of
the existing file, I don't see that as a big problem. I think that
"rpmnew" files are deleted when uninstalling a package (should check in
Maximum-RPM but I'm lazy).
Gr�goire
