On Sep 12, 2016 2:36 PM, "Tony Marston" <tonymars...@hotmail.com> wrote: > > Sent: Sunday, September 11, 2016 8:32 PM > >To: Tony Marston ; Stanislav Malyshev ; internals@lists.php.net > >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle > > > > > >On 09/11/2016 10:47 AM, Tony Marston 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 > >>> Hi! > <snip> > >> 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. > > >again, nobody is trying killing PEAR/PECL. do we need to use strong > >terms to make that clear ? > > To the average user if something is marked as deprecated it is the same as saying “do not use this feature any more”with the very next step being to kill it off completely. > > If you are not going to kill it then why deprecate it?
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.
