Re: Re: move PEAR to PHP 5-only?
| From: | Justin Patrin | Date: | Sat, 01 Oct 2005 21:05:21 +0000 |
| Subject: | Re: Re: move PEAR to PHP 5-only? | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev php.pear.core |
| Request: | Send a blank email to pear-dev+get-40031@lists.php.net to get a copy of this message | ||
On 10/1/05, Joe Stump <joe@joestump.net> 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.
>
No, adding a new dependency is not a BC break, and no, changing your
dependency to a newer version of a package is not a BC break, but
you're all missing one very large problem. PHP is not a PEAR package
and cannot be treated as such.
Not only does PHP5 break BC, it *cannot* be used in conjunction with
PHP4. PEAR's rules allow 2 versions of a package to be used in
parallel. You can't do the same with PHP versions.
So, since PHP is essentially a "non PEAR dependency" and does not
conform to PEAR's BC rules we need to treate it differently.
--
Justin Patrin