[Cooker] rpm still creating .rpmnew for unchanged config files

[Brian J. Murrell]

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.


-- 
Brian J. Murrell