2016. szept. 2. 21:58 ezt írta ("James Gilliland" <neclim...@gmail.com>):
>
> On Fri, Sep 2, 2016 at 2:33 PM Davey Shafik <m...@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.
> >
> > - Davey
> >
> Will composer/pickle address the unsolved PHP compatibility issue that
> makes pecl a pain following the PHP 7 release?You are probably talking about https://bugs.php.net/bug.php?id=71224. My understanding is that when fetching the packages from pecl.php.net pickle would still have the same problem ( https://github.com/FriendsOfPHP/pickle/issues/133) but if pecl authors start adding composer.json to their repos you can describe the php version dependency for the given extension on a per tag/version basis. I still think that it would be worth implementing https://bugs.php.net/bug.php?id=71224
