Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95914
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <DB3PR04MB2038093881B1A4A5C9BCBD8BBFC0@DB3PR04MB203.eurprd04.prod.outlook.com>
References: <DB3PR04MB2038093881B1A4A5C9BCBD8BBFC0@DB3PR04MB203.eurprd04.prod.outlook.com>
Date: Sun, 11 Sep 2016 06:44:19 -0400
Message-ID: <CAL+t6cHhZv1tqQFm1epBofPzDHV_f0VWG8WFv83s6dhY1JJKfg@mail.gmail.com>
To: Tony Marston <tonymarston@hotmail.com>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01229296dd79a4053c390fc9
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: theanomaly.is@gmail.com (Sherif Ramadan)

--089e01229296dd79a4053c390fc9
Content-Type: text/plain; charset=UTF-8

On Sun, Sep 11, 2016 at 4:47 AM, Tony Marston <tonymarston@hotmail.com>
wrote:

> Sent: Saturday, September 10, 2016 7:47 PM
> >To: Tony Marston ; internals@lists.php.net
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
> composer/pickle
>
>
> Then I suggest that those who are so anxious to see of death of PEAR/PECL
> should be forced to provide a viable alternative first. Otherwise they
> would be just like those stupid politicians who try to force commuters out
> of their private cars and into public transport without realising that the
> existing public transport system is NOT a viable replacement and is
> incapable of taking on the extra load.
>
>

I just want to say that PEAR as a source repository, has been dead for
quite some time. It's filled with outdated code that has hardly seen any
maintenance in years, and nobody really contributes to it anyway.

PEAR/PECL as a package manager has historically had little utility to the
average user apart from installing those PECL extensions which aren't
packaged by a particular user's distribution repository. Certainly hasn't
had any real viability in years. Trying to replace something that's
inherently non-viable with a viable-alternative seems like a pretty moot
point.

--089e01229296dd79a4053c390fc9--