Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95611 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22484 invoked from network); 4 Sep 2016 08:38:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2016 08:38:12 -0000 X-Host-Fingerprint: 90.254.7.7 unknown Received: from [90.254.7.7] ([90.254.7.7:26252] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A8/67-32927-27DDBC75 for ; Sun, 04 Sep 2016 04:38:11 -0400 Message-ID: To: internals@lists.php.net References: In-Reply-To: Date: Sun, 4 Sep 2016 16:38:06 +0800 Lines: 1 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response 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.254.7.7 Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: TonyMarston@hotmail.com ("Tony Marston") "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. Any proposed replacement which does not have a web interface I'm afraid is totally unacceptable. Command line interfaces went out of fashion when the Windows OS was first released, and anyone who still insists on using one has not joined the rest of the world in the 21st century. I do NOT want the replacement PEAR library to be mixed in with my application code. I do NOT want the replacement PEAR library to update itself in the background. It has to be under MY control or I simply won't install it. It has to be 100% stable, and I'm not sure that composer/pickle fit the bill. There may be a small number of developers out there who think that composer is the best thing since sliced bread, but I'm not one of them, and I strongly object to a small number of developers having the ability to impose their personal preferences on the rest of the community. -- Tony Marston