Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle

From: Date: Mon, 12 Sep 2016 12:05:09 +0000
Subject: Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-95941@lists.php.net to get a copy of this message
On Sep 12, 2016 6:51 PM, "Nikita Popov" <nikita.ppv@gmail.com> wrote: > > On Mon, Sep 12, 2016 at 1:42 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote: >> >> On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans <derick@php.net> wrote: >> >> > On Mon, 12 Sep 2016, Pierre Joye wrote: >> > >> > > This RFC is about stop bundling it with the php releases and propose >> > > composer/pickle instead. Everything else has nothing to do with this >> > > RFC (aka web frontend, what happens or not on pear.php.net, its >> > > packages, etc.). >> > > >> > > To all: please re focus to the topic. >> > >> > It's curious to see though that the off-topic comments get replies, but >> > few real concerns do from the RFC author - such as not removing >> > something before we have a confirmed alternative. I'd like to trial >> > pickle first for a few releases and only then see whether to remove the >> > PEAR/PECL installer. >> >> >> yeah, unfortunately when the thread gets flooded with off-topic mails it is >> easy to miss some replies in the noise. >> I do agree that it would be better and easier to only vote for bundling >> pickle instead of also voting for unbundling PEAR at the same time. > > > Is it (technically) possible to unbundle PEAR while leaving PECL? Not really without actually bundling pear but not provide the pear cmd. Also pickle works with pecl.php.net as long as it has a package.xml v2, which is required since quite some time on release.

« previous php.internals (#95941) next »