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

On Sat, 1 Oct 2005 13:38:50 -0700 joe@joestump.net (Joe Stump) wrote: > > 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. > > No, it's not. A BC break is when the *API* changes, not when a > dependency changes. If this was the case then adding any new > dependency would constitute a BC break, which is just silly. As Greg > already stated the PHP5 version of PEAR won't install on a PHP4 > system. I think you miss the point. Package 1.4: class foo { var $a; } package 1.5 { public $a; } Does package 1.5 will work with php4? No. This is 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. > > So is anyone using anything before PHP version 4.2 - what's your > point? As php 4.2 or earlier is not supported anymore, there is many critical issues in many of these releases (security related), I see no problem to update. We already did that in the past, bumping from 4.0 to 4.1 or 4.2. I also think that you should take a closer (and realistic) look to the php5 usage statistic. Our goal is not to promote php5, but to provide reliable tools to manage packages. I agree that the next big step for the installer is to provide a php5 only installer, but it will be a php 5.1 anyway, not 5.0.x, if not something later. So trying now to force php5 usage as the 1st really useable php5 release (5.1) is not even out is pure ignorance. Regards, --Pierre