Description: ------------ Currently, it is often a problem finding the PEAR installation as the PEAR Installer might report one version with "pear list" and actually be running an older one as reported by "pear -V" Basing the PEAR location on simpler search criteria such as include_path makes more sense. Also good would be pear /path/to/pear install packagename where we can explicitly specify where to install a package.

It's worth noting that this causes particular grief when using custom file roles and other PEAR-core addons (e.g. PEAR_Command_Packaging). "pear config-create <path> <configfile>" followed by "pear -c <configfile> <command>" works fine in most cases for creating a "sandboxed" PEAR, but fails when it comes to custom file roles or other PEAR-core addons, since these need to require() files from the PEAR installation.

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.