Re: memory usage issues in PEAR 1.4.0
| From: | Greg Beaver | Date: | Fri, 04 Mar 2005 16:58:11 +0000 |
| Subject: | Re: memory usage issues in PEAR 1.4.0 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-36538@lists.php.net to get a copy of this message | ||
Alan Knowles wrote:
This will mean that when upgrading PEAR, fatal errors will always occur if any major changes are made in lazy-loaded files, because the newer file is included. >For instance, downgrading to 1.3.5 from 1.4.0 destroys the installation without the non-lazy loading. Hence, if ($package == 'PEAR') lazy load all files before upgrading? - it's looks alot like an edge case scenario that's affecting more general usage, and maybe a contributor to pearweb load issues?, It seems like it might be worth investigating to try and solve this?How would you determine whether it is necessary? In PEAR_Installer::install() is the only location you can be sure. So would I add a whole bunch of include_once() statements like so: if ($package == 'PEAR' && $channel == 'pear.php.net') { include_once ..... } ? pearweb doesn't require any PEAR installer classes except to handle release uploads, I doubt this is a contributor. Greg