Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95713 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50124 invoked from network); 7 Sep 2016 07:52:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2016 07:52:16 -0000 X-Host-Fingerprint: 90.255.4.109 unknown Received: from [90.255.4.109] ([90.255.4.109:13392] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/26-18051-E27CFC75 for ; Wed, 07 Sep 2016 03:52:14 -0400 Message-ID: To: internals@lists.php.net References: In-Reply-To: Date: Wed, 7 Sep 2016 08:52:09 +0100 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 90.255.4.109 Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: TonyMarston@hotmail.com ("Tony Marston") "Pierre Joye" wrote in message news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=N1rjmspoFmHBEbDHxg@mail.gmail.com... > >Hi Tony, > >On Tue, Sep 6, 2016 at 2:17 PM, Tony Marston >wrote: >> "Niklas Keller" wrote in message >> news:CANUQDCjeH45_2aEq74CCEOY4xc3xJ0o_+yRQ2NVy0K2VdOXFBQ@mail.gmail.com... >> >>> >>> Tony Marston schrieb am So., 4. Sep. 2016, >>> 10:38: >>> >>>> "Rowan Collins" wrote in message >>>> news:b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com... >>>> > >>>> >On 02/09/2016 20:32, Davey Shafik wrote: >>>> >> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and >>>> >> remove >>>> >> in 8.0), as well as add composer/pickle (optional in 7.2, default in >>>> >> 7.3+) >>>> >> in their place. >>>> >> >>>> >> https://wiki.php.net/rfc/deprecate-pear-include-composer >>>> > >>>> >Hi Davey, >>>> > >>>> >I think this is a sensible idea. It basically accepts the reality that >>>> PEAR >>>> >is no longer the main place new users of PHP should look for 3rd-party >>>> >code. >>>> > >>>> >Thinking about the responses so far, I thought it would be useful to >>>> >enumerate just what PEAR is, and what is being proposed for removal. >>>> >It >>>> >might even be worth adding a version of this to the RFC, in case it >>>> reaches >>>> >a wider audience who won't see this discussion. >>>> > >>>> >As I understand it, PEAR is: >>>> > >>>> >A1) A command-line package management tool for installing and updating >>>> >packages of PHP code over the Internet. >>>> >>>> Incorrect. There is a web interface which I use EXCLUSIVELY to maintain >>>> the >>>> contents of my PEAR library. >>> >>> You only work in a web interface instead of an editor and version >>> control >>> system? >> >> PEAR does not have a version control system. My software has an SVN >> repository, but that is totally unconnected with PEAR. My choice of >> editor >> has no bearing on the issue. > >It has, whether you need it or not is not really relevant to this >discussion. > >> I use the web interface to maintain PEAR on my local machine, and my >> hosting >> companies provide a web interface in their control panels. > > >Happy to see there are still users for this tool, Christian and I had >good fun writing it. Also you should know that this package is dead, >it has no acttve maintainer (I was the last one) and has some >limitations from to begin with, also was very handy at time especially >for shared hosting without shell access. > Typical. You create a useful tool, get your users hooked, then walk away and leave them dangling. -- Tony Marston