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

From: Date: Sat, 01 Oct 2005 17:29:29 +0000
Subject: Re: Re: move PEAR to PHP 5-only?
References: 1 2 3  Groups: php.pear.dev php.pear.core 
Request: Send a blank email to pear-dev+get-40021@lists.php.net to get a copy of this message
On 10/1/05, Pierre <pierre.php@gmail.com> wrote: > On Sat, 1 Oct 2005 19:19:25 +0200 > pierre.php@gmail.com (Pierre) wrote: > > > On Sat, 01 Oct 2005 08:57:22 -0700 > > greg@chiaraquartet.net (Greg Beaver) wrote: > > > > > Hi all, > > > > > > How do PEAR developers feel about moving PEAR 1.5 to PHP5-only? > > > > > > -1 here > > > > > > > PEAR 1.4.2 will be out shortly, with all pecl issues fixed, which > > > works in PHP 4.x just fine. > > > > > It would give me no end of pleasure to stop actively developing in > > > PHP 4. > > > > Same here, but it is simply not possible for so many obvious reasons, > > one of those being BC. The same problem exists in PHP itself for PHP4 > > and PHP5, but I still have to fix 4.4, 5.0 and 5.1. > > Forgot to mention what I already asked weeks ago. > > Once 5.1 is out, we can make 4.3 the minumum requirements. But droping > 4.x support in any PEAR 1.x releases is not possible, or we drop all > the rules which make the quality of our releases. > I agree. Dropping support for PHP4 constitutes a BC break. Think of Joe Developer, who upgrades PEAR-1.4 to PEAR-1.5. Oops, PEAR breaks. This is what defines a BC break. Now, it is certainly possible that you can add a PHP5 dependency to the PEAR package.xml, but this is only a quick fix for the above problem. Anyone using PHP4 will be shut out from updates and bug fixes in the 1.x line. To move to only PHP5, PEAR will have to move to PEAR2 as this is a BC break. You're welcome to take the current code, make it PHP5-only, and rename it PEAR2, but I doubt this is what you want. -- Justin Patrin

« previous php.pear.dev (#40021) next »