Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | David Walker | Date: | Fri, 02 Sep 2016 20:40:56 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95591@lists.php.net to get a copy of this message | ||
On Fri, Sep 2, 2016 at 1:33 PM Davey Shafik <me@daveyshafik.com> wrote:
> Hi internals,
>
> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
> in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+)
> in their place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-composer
+1
A bunch of years back I tried contributing to a handful of PEAR_Auth
packages and the 'maintainer' rejected them all on the basis of the PEAR
library was mothballed with recommendation to use ZendFrameworks Auth
packages. I know at least where I work we're migrating everything off of
PEAR in deference to community maintained packages in composer.
The only negative I could possibly see is a lack of a central, for lack of
a better term, authority of PHP preferred packages for the multitude of
services PEAR offers. But I don't necessarily see this as a major issue
with the multitude of frameworksµframeworks that modularize all their
bits and places like composer/packagist maintaining a growing list of
packages. I guess PEAR served that purpose years ago in a more isolated
PHP source environment, rather than today where it's heavily tracked and
distributed.
Cheers
--
Dave