The RPM package manager seems to have two different mechanisms for handling configuration files. It appears from my very quick reading about RPM works that a file can be identified in the package as a configuration file. This file can also be classified as either replaceable or non-replaceable. According to the RPM docs an older, modified, configuration file will not be overwritten.
1.) If a replaceable configuration file is installed the existing, modified configuration will be renamed '.rpmsave' and the new configuration file will be installed. 2.) If a non-replaceable configuration file is installed the existing modified configuration file will not be touched and the new configuration will be installed as '*.rpmnew' (I couldn't find any reference to *.rpmnew in the MAX-RPM docs, only in discussions found through search engines) If this is true, what is the purpose for the up2date configuration item that can be selected which will force packages into the skip list if a configuration file has been changed? It appears to be redundant. Regards, Mike Klinke -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
