Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95854
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <e441c74d-7c4a-393a-fa05-21b9f80fd214@lsces.co.uk>
References: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk>
 <CANUQDCh=xC5G2FS2a-jm3aKATwV1BuOhd+AQiCq7tnMUvruFcA@mail.gmail.com>
 <fc0df908-0e9d-e748-70cb-9d9a6e8d4ee6@lsces.co.uk> <CAH-PCH5FadFFygmXQE35Fzr6sDniG8rdsnVvWA9FYE+404RYog@mail.gmail.com>
 <e441c74d-7c4a-393a-fa05-21b9f80fd214@lsces.co.uk>
Date: Fri, 9 Sep 2016 14:32:53 +0200
Message-ID: <CAH-PCH6vE4EV0YaX-q_USUdH1KcsemMhbvN=e9iKqCpEPnrHfw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7ba9790c7345c0053c1258e0
Subject: Re: [PHP-DEV] Modern practices ...
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7ba9790c7345c0053c1258e0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 9, 2016 at 1:45 PM, Lester Caine <lester@lsces.co.uk> wrote:

> On 09/09/16 12:35, Ferenc Kovacs wrote:
> > but please, this is really offtopic on this list.
>
> See my other reply ...
> and composer global mode as provided out of the box is NOT an
> alternative to installing the sort of production and development -
> command line - tools that PEAR currently manages happily. I AM trying to
> learn composer, and I can see now how it can be used, but simply passing
> the buck to getcomposer is not the way to use it for a default PHP
> installation.


composer is proven to be capable managing those use-cases but it isn't our
duty to write out the detailed migration guides for every usecase between
PEAR and composer.
our duty as the php-src group is that we provide a way which allows the
management of the pecl extensions (pickle install and maybe providing an
alternative for pecl package) and tell people how can they install PEAR if
they still need it (https://pear.php.net/manual/en/installation.php)
for the record most distributors already decouple PEAR from the base php
install (php-pear is a separate optional package on debian/ubuntu, the
windows binaries doesn't have PEAR at all, you have to manually install it
there, etc.) and from the php-src point of view we only use it to provide a
way of installing pecl extensions, which will be solved with pickle so
while educating people to migrate their workflows from PEAR to composer is
a noble goal, but it isn't our responsibilities and we don't have to solve
that to be able to replace our php c extension management tool shipped with
the core.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7ba9790c7345c0053c1258e0--