Description: ------------ Bug #12108 is a great new feature which works fine. However it does not give any kind of warning when doing a PEAR upgrade/install which is going to handle a config file "specially". This is particularly important when NOT installing a new config file in the "proper" location but instead installing it as "xxx.new-X.Y.Z", because the user will not realise (unless they are exceptionally diligent) that they need to go and manually check/merge "xxx" and "xxx.new-X.Y.Z". Test script: --------------- For example, consider I have a package Foo-1.2.3 with a file "foo.cfg" that has role="cfg". A new package, Foo-1.3.0, has a different config file. A user upgrades to Foo-1.3.0 Expected result: ---------------- warning: foo.cfg is being installed as foo.cfg-1.3.0; you should manually check and merge changes as appropriate Actual result: -------------- The user receives no warning that the new config file is being installed as foo.cfg-1.3.0

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.