On Mon, Sep 12, 2016 at 1:51 PM, Nikita Popov <nikita....@gmail.com> wrote:
> On Mon, Sep 12, 2016 at 1:42 PM, Ferenc Kovacs <tyr...@gmail.com> wrote: > >> On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans <der...@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? > > Nikita > not really, we pull the pear installer directly from https://pear.php.net/install-pear-nozlib.phar there is no option to only install the pecl stuff, so it would either require a major rewrite on pear-core and a new release, or maybe we could try something like doing a standard install then proceed and delete out files (like pearcmd.php) as part of make install but that would be still sucky. and we still have most of PEAR core around and still no pecl package install support on windows. with bundling pickle we could remove the PEAR dependency and pickle would also work on windows. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
