Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95624
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAO3MkaDcB8qC-6BSySk4BLaQVqZN7n6sSBMrBaJa4ddyCy5Cdw@mail.gmail.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <CAO3MkaDcB8qC-6BSySk4BLaQVqZN7n6sSBMrBaJa4ddyCy5Cdw@mail.gmail.com>
Date: Mon, 5 Sep 2016 02:09:37 +0200
Message-ID: <CAH-PCH5WE3Ce7o+A8EFj=eHgCn9ArNgCuBRxPH26M0tkQWjHGg@mail.gmail.com>
To: James Gilliland <neclimdul@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114428b8f4a5b6053bb77e4e
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a114428b8f4a5b6053bb77e4e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2016. szept. 2. 21:58 ezt =C3=ADrta ("James Gilliland" <neclimdul@gmail.com=
>):
>
> On Fri, Sep 2, 2016 at 2:33 PM Davey Shafik <me@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=3D71224.

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=3D71224

--001a114428b8f4a5b6053bb77e4e--