Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.14

Bug #12945 PEAR_Registry::setConfig() does not set install path
Submitted: 2008-01-21 12:05 UTC
From: cweiske Assigned: cellog
Status: Closed Package: PEAR (version 1.7.0RC2)
PHP Version: 5.2.5 OS:
Roadmaps: 1.7.2    

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 44 - 29 = ?

 [2008-01-21 12:05 UTC] cweiske (Christian Weiske)
Description: ------------ When using $pear_registry->setConfig() to change the configuration of an registry object, using getPackage() still fails because the registry relies on the install_dir set in the constructor. I expect the registry to use the installation directory of the current config -> patch attached.


 [2008-01-29 03:43 UTC] cellog (Greg Beaver)
Christian, this patch affects a critical portion of the core, and breaks 20 unit tests. I'm postponing until 1.7.1 at the earliest.
 [2008-05-14 04:16 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the 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. I took your patch and added cleverness, making the reset of install_dir optional, enabled by default. This way, one can disable this for critical stuff like install_root and company. Voila, all existing tests pass with the change, so I'm happy :)