Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95609
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain daveyshafik.com from 209.85.220.180 cause and error)
MIME-Version: 1.0
Sender: me@daveyshafik.com
In-Reply-To: <f79f5c81-c0e4-cd51-8d91-24f66e4191fa@gmail.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com> <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk>
 <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com> <eed6f3c1-96eb-65ef-815e-4026048aaeca@lsces.co.uk>
 <f79f5c81-c0e4-cd51-8d91-24f66e4191fa@gmail.com>
Date: Sat, 3 Sep 2016 17:54:01 -0700
Message-ID: <CANaX5ndOgHR0U5Dd_zgp6BFR2Lo4NpidbnTDnJ-NgLrii0b_2g@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114fe61adef500053ba3ff23
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: davey@php.net (Davey Shafik)

--001a114fe61adef500053ba3ff23
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 3, 2016 at 2:53 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 03/09/2016 19:44, Lester Caine wrote:
>
>> So this RFC is simply proposing that PHP-FIG becomes the standard for
>> writing PHP code?
>>
>
> No, that is not at all what this RFC is proposing. The RFC is simply
> proposing to stop bundling the command-line tool "pear" with default PHP
> builds.
>
> The PEAR coding standards will still exist, the packages created accordin=
g
> to them will still be usable, and you'll still be able to download pear, =
or
> pyrus, to access them. You could also use composer to access most of them=
,
> and publish packages adhering to that style on packagist.org, or pretty
> much any platform you want.
>
> The only reason I mentioned PHP-FIG is because they are trying to write a
> modern standard for writing interoperable PHP libraries, which is what yo=
u
> asked for.
>
> I guess we could have a philosophical debate about what it means for
> something to be "the standard" rather than "a standard", and whether PEAR
> was "more official" than PHP-FIG, and just who gets to decide what PHP is=
.
>
> But once again, I find myself being drawn into an off-topic debate about
> coding styles, and I would like to apologise to Davey as it has nothing t=
o
> do with his RFC.


No need to apologize, thank you for defending my idea and so eloquently =E2=
=80=94 I
will amend the RFC with your earlier suggestions; being as I will do so
almost verbatim, would you mind being added as a co-author? I think it's a
substantial contribution :)

- Davey

--001a114fe61adef500053ba3ff23--