Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | Rowan Collins | Date: | Tue, 06 Sep 2016 10:40:25 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95694@lists.php.net to get a copy of this message | ||
On 06/09/2016 11:18, Derick Rethans wrote:
One of PHPs biggest strengths is the availability of an extension for nearly everything. There are *1000s* out there. Some made by single people, some by small groups of people, or some by large companies. You can't expect *all* of these extensions to be available through distribution's packages.By the same reasoning, most of them won't be available on pecl.php.net either. I'm curious, do people often run their own PECL-compatible "channel" servers?
They'd still need to run the equivalent to "pecl" to install these manually build extensions. Or at least the "pecl download" variant.Not really, the ones I've used come as a tarball, use "phpize" and standard build tools, and have a "make install" to put the .so file in the right place. Then you just have to add "extension=foo.so" in the appropriate ini location (which you have to do after pecl install anyway). I agree that a stable tool for installing from pecl.php.net should always be included, though. Regards, -- Rowan Collins [IMSoP]