Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | Pierre Joye | Date: | Wed, 07 Sep 2016 12:18:49 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95743@lists.php.net to get a copy of this message | ||
On Sep 7, 2016 6:24 PM, "Lester Caine" <lester@lsces.co.uk> wrote:
>
> On 07/09/16 12:02, Pierre Joye wrote:
> > One point, pickle does not need composer to run.
> >
> > pickle install memcache will install the memcache extension (windows
> > binaries, from pecl.php.net, etc) straight away.
>
> That one is useful to know. I have all my own active pear stuff under
> the code repository and so plain PEAR is less of a problem other than
> where it's hard coded into legacy installers. And I will just need to
> manually add it if needed. Windows extensions are the area where I've
> not been able to build my own or some time because I need a clean build
> system working on W10, which is part of the reason I am concerned if the
> likes of interbase is no longer available pre-compiled. I have no
> problem playing on Linux, it's just keeping windows clients alive and
> the existing set-up just works.
The service we provide to build binaries for pecl.php.net remains and will
as long as pecl.php.net is up and running (and it is going to be for a very
long time).
We simply extend this service to the growing amount of extensions only
available on GitHub&co.