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

From: Date: Wed, 07 Sep 2016 15:49:18 +0000
Subject: Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-95757@lists.php.net to get a copy of this message
Regards, Mike > On 02 09 2016, at 21:32, Davey Shafik <me@daveyshafik.com> wrote: > > Hi internals, > > 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 > > I highly recommend reading the twitter poll and accompanying thread at > https://twitter.com/dshafik/status/756337267547832320 > > I believe that pickle solves the issues with regards to pecl, and have run > the idea passed Jordi and Pierre. Both are fine with this RFC. :) > > I understand that adding in composer/pickle is just setting us up for > having a future "Deprecate composer/pickle & Replace with foo/bar" RFC, so > I've proposed the voting reflect that some people will just want to > deprecate/remove pear/pecl and not replace them at all. > > I'm also proposing voting choices around the optional/default introduction > of composer/pickle. +1 on stabbing the PEAR installer from the source distribution. -1 on adding anything else. Composer is as easy to install separately as PEAR from their origin as well as from OS distributions these days. On a side note, we should look into evolving ext/phar to a plugin based system, not the hard coded foreign feature sink it currently is (with regards to compression and signing support at first, with the underlying file format being next). Cheers, Mike

Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc
« previous php.internals (#95757) next »