Re: Re: move PEAR to PHP 5-only?

Justin Patrin wrote:

Why? If BC is kept, there is no need to bump the version number. Recall that you can hapilly run 1.4 (under PHP4) and 1.5 (under PHP5) on the same server, by configuring different PEAR directories for the different PHP versions.

I am still of the opinion that upping the dep from PHP4 to PHP5 effectively breaks BC since PHP5 breaks BC with PHP4.

We have barely the ressources to maintain a single version of PEAR. We can hardly assume that PEAR 1.4.2 will be free of important bugs and more importantly security issues. So moving to a PHP5 only PEAR 1.5 is effectively killing PHP4 support. For what? The PEAR base class was made irrelevant for PHP5 packages because if that (imho dreadful) exception RFC. So why do we care if the freaken CLI installer is E_STRICT? Its a distribution mechanism not a runtime environment. Now the problem is that the PEAR installer is run usually with the configuration of a the runtime environment where people might have E_STRICT enabled. Rewriting PEAR code on install time or whenever to E_STICT is also insane. So the solution to me seems to see about ways of easily calling the PEAR installer in a non E_STRICT environment. I am sure there are ways to make this possible. PEAR2 can be PHP6 only for all I care. regards, Lukas