Re: temporary solution

On Sun, 2005-03-06 at 22:21, Greg Beaver wrote: > There is one thing I coded that can probably be lazy-loaded, and that is > the stuff for generating a package.xml and to a certain extent for > validating the package.xml. This will only save about 1 MB, which is > not nearly enough for Alan's goal of matching what 1.3.x did. Nahh we shouldn't try that, just getting it below 8M use is enough for the time being I'd say, that would allow things to work fine on PHP4, in most cases anyway :-) PHP5.0 is below 8M (well barely but still) and on 5.1 we had, what 4.3M ? When I can run pecl <insert stuff here> with out putting high mem limit then I'd be quite happy for the matter of fact :-) Also there is some mem problem when upgrading many packages at a time. I was just now doing upgrade-all with state set to alpha and voila 13 packages needed upgrade, after getting 11 similar to this one upgrade-all ok: channel://pear.php.net/HTTP_Header-1.1.2RC1 then I got this error message (as people can see the mem limit is in 20M!) PHP Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 24 bytes) in /usr/share/pear/PEAR/Installer.php on line 270 Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 24 bytes) in /usr/share/pear/PEAR/Installer.php on line 270 Allowed memory size of 20971520 bytes exhausted (tried to allocate 0 bytes) Couldn't this be avoided somehow ? I mean isn't there something that could be freed in between ? If not then so be it :-) We can't get everything we want ;) > No, channels can't be optional in any circumstance, it would require a > 100% redesign and another year to 1.5 year delay to get it stable. > > The only way to drop memory usage properly is to follow Mozilla's route > and completely break BC. > > 1) no support of package.xml 1.0 whatsoever > 2) no support of PHP 4 > 3) no support for the existing registry format. > > This will allow a ton of the weight to be shouldered by the xml stuff > built into php 5, and would drop PEAR back into the 3-4 MB range easily. Like said above 5.1 already gets that goal WITH the current code :) I assume most PHP5 people will upgrade to 5.1 shortly after it's out so we're more focusing on PHP4 (That's how it looks anyway) But couldn't we do at least 3) ? We could either make a special "package" (no included in PEAR) that would be migration thing so we wouldn't have to include that in the PEAR package or anything, this would mean people that are moving from 1.4.0aX or 1.3.X have to run this script prior to upgrading to next 1.4.0 version that wouldn't support that registry and to ensure this we could run some script in the installation of 1.4.0 that would die if the old registry is still present. Just a idea to bounce of you people but it seems it would solve some of our problems, no ? :) - Helgi