Re: PEAR 1.4.0a9 fixes memory problems in my tests

Lukas Smith wrote:

Greg Beaver wrote:

Hello, For all standard commands, including Web Installer-used commands like list-all, list, install/upgrade/upgrade-all and so on, PEAR 1.4.0a9 has a significantly lower memory footprint, and clocks in under 8 MB.

good to hear might it be possible to add a debug mode config setting that outputs the memory usage at the end of the script execution?

Packaging can still take oodles of memory because of the memory hit by token_get_all(). This is especially true for packages like PEAR that have both a package.xml 1.0 and 2.0, as this puts memory usage at about 6 MB prior to source code analysis. However, I am under the impression that most devs doing packaging will be doing this on a development machine that they control, so unless my impression is wrong, this should not be an issue, as the "peardev" command can be used for those who wish to keep memory_limit at 8MB in php.ini.

Yes, I think this is a valid assumption. BTW: is it possible to combine any command with a state override? For example what if I want to get the list of all upgradeable packages with state beta or higher?

I believe list-upgrades is aware of preferred_state. If you want an option, well I would first check with "pear help list-upgrades" and if one isn't there, a feature request may be in order. Greg