On Fri, 2 Sep 2016, 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 > > I highly recommend reading the twitter poll and accompanying thread at > https://twitter.com/dshafik/status/756337267547832320
I don't think that question is phrased correctly. It is asking about PEAR, and *not* PECL. I don't think we should deprecate *anything*, until pickle is deemed stable, and all issues with it are resolved (if there are any). So instead of suggesting to deprecate something, perhaps it would be a better idea to add pickle first - and only *then* even begin to figure out whether it's better than "pecl" for installing PHP extensions. "At the same time, we'd like to include composer/pickle as optional (under build flags –with-composer and –with-pickle) for 7.2, then enabled by default in 7.3. " I don't think we should bundle composer, and also don't think it should be an optional install. If it's an add-on (action required to enable pickle), people won't do it, and nobody tests it - and continues to use "pecl", which allthough not ideal, does do the job excellently. > 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. :) What are these issues with the "pecl" installation tool? The RFC has no mention of this. One of them could be that it gets very few maintenance, and it's a little bit of a pain to update. Anything new should at least solve that. That also means there need to be at least 3+ people that know it well enough to be able to update, maintain and roll out releases. > 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. You can't really ship PHP without a way to install extensions though! And it should work also work out of the box, without any other tricks or steps to make it working. That means, not having to run "composer install" in order to get a working "pickle" tool. A phar might be an idea. All in all, I think it is premature to want to remove something, without fully understanding the replacement tool. So, the first step would be to *add* something, and not call for the removal of things. cheers, Derick
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
