Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | Dan Ackroyd | Date: | Mon, 05 Sep 2016 09:51:09 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95637@lists.php.net to get a copy of this message | ||
On 2 September 2016 at 20:32, Davey Shafik <me@daveyshafik.com> wrote:
> 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.
Even if Pear and Pecl overlap and share code, it would be better to
focus on the end-user capabilities and have separate RFCs for altering
those capabilities, rather than just trying to do everything in one
RFC. i.e. have:
One RFC to deprecate then remove the ability to install Pear userland
code modules.
A second RFC to deprecate Pecl and optionally start using Pickle.
Can you clarify one thing though - am I correct in that Pickle is
completely userland code? So why does it need to be 'shipped' with
PHP. Why can't it be a separate download?
cheers
Dan
> pickle would still have the same problem (
> https://github.com/FriendsOfPHP/pickle/issues/133)
Needs moar macros:
https://travis-ci.org/mkoppanen/imagick/builds/150948947