Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | Stanislav Malyshev | Date: | Mon, 05 Sep 2016 04:19:29 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95628@lists.php.net to get a copy of this message | ||
Hi!
> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
What would be achieved by this? I'm not sure about status of PEAR -
frankly, didn't touch it for a long time - but if composer replaces most
of it, it may be ok to remove by-default install of pear tools. Though
I'm really not sure what "deprecating" means and what it's going to
achieve.
Pickle main README says:
Pickle is a new PHP extension installer. It is based on Composer and the
plan is to get Composer to fully support it.
How is that plan going? I see the pull req it refers to still open,
which means it is still not complete. Should it be completed before we
recommend it as an only solution?
> in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+)
> in their place.
Add in which meaning? Distribute composer package with PHP source?
Wouldn't that add maintenance load to keep it up-to-date?
If that means get some way to d/l newest stable composer, e.g. when
installing php, that probably would be a great idea. Does not require
removing stuff though.
--
Stas Malyshev
smalyshev@gmail.com