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

From: Date: Sun, 11 Sep 2016 10:44:19 +0000
Subject: Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-95914@lists.php.net to get a copy of this message
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.

« previous php.internals (#95914) next »