Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95592
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
Date: Fri, 2 Sep 2016 15:17:20 -0600
Message-ID: <CAObuZds2ej5LYQFg2rNEv7bKzCMpeA8PVGVrKVgkOOs-xskX0Q@mail.gmail.com>
To: Davey Shafik <me@daveyshafik.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114302081d644c053b8cdbf2
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: derokorian@gmail.com (Ryan Pallas)

--001a114302081d644c053b8cdbf2
Content-Type: text/plain; charset=UTF-8

On Fri, Sep 2, 2016 at 1:32 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.
>

I like the idea, my only concern is that pickle hasn't been committed to
master in many months and the build is listed as failing.  In fact the last
release (v0.4 from what I can tell) also shows the build as failing?


> - Davey
>

--001a114302081d644c053b8cdbf2--