Description: ------------ The new cfg role (bug #12108) is great. However it works a little simplistically in some cases. Consider a package Foo-1.2.3 with file "foo.cfg" with role "cfg". The user installs Foo-1.2.3 from scratch. The user does NOT modify foo.cfg Foo-1.3.0 is released, that has a different foo.cfg. At the moment, PEAR will leave foo.cfg in place and install the new foo.cfg as foo.cfg-1.3.0. However this is not the behaviour that one generally wants. Because the user *has not changed* foo.cfg, Foo-1.3.0 should overwrite the original foo.cfg. This is how RPM has worked for many years, and it "makes sense". However it does require that PEAR stores internally somewhere the MD5 sum of foo.cfg upon installation/upgrade of Foo and then checks this when Foo is upgraded.

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.