Description: ------------ Currently, we cascase configuration files so that there is a user configuration file (usually .pearrc/pear.ini) and a system configuration file (usually pear.conf/pearsys.ini). Now that configurations are tightly bound to the php_dir location, it becomes impossible to cascade configurations. More useful would be the ability to cascade installations based on include_path. In other words, if a dependency is not satisfied, allow the installer to search in a parent registry to see if the dependency is installed there. This way, a master PEAR installation of base classes could be used as a parent to a number of child PEAR installations.

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.