Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95608 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23306 invoked from network); 3 Sep 2016 21:53:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2016 21:53:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-wm0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:36985] helo=mail-wm0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/55-32927-4664BC75 for ; Sat, 03 Sep 2016 17:53:41 -0400 Received: by mail-wm0-f54.google.com with SMTP id v143so80525140wmv.0 for ; Sat, 03 Sep 2016 14:53:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=0U/X+KOoR42hCEMU88injGYZ+8D12I0CpEmZpZgVXEk=; b=l6sI0t/KL4mVgJQz0aZoZnT9xqBIDVAGj+fhwuRkJOVE0kWPwgrUhhdffvk1uctI19 k2X6J1LIyUsjNR2hrfaNW9pe0Uf3MFjkuzL9Po1WdJmjD18NTbau0VLVa41PjC5fYUI5 cinFkag5Yn4pn/gvmKG/pACxGq3qopE1eJtKE1VdaLwVAw6bUltLLazdrelWx9Y0fr1C pmhWNdYLO4eA+TyUnkGFBd/BbRWbhwbFqLCMqXMWA0KOeGvsFNDEJ0k6Z69f3XEeAnov 4SeMoVJJ3ah2zjgXJeY6zRIu8P+E0CoSLUYvNmS7yp4HknwUz8APn7gvJLTWpeIYP8uL eZ8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=0U/X+KOoR42hCEMU88injGYZ+8D12I0CpEmZpZgVXEk=; b=CLwJg+PcFpbF7owSUvE2ycp+MWpRP0y4bP3DOmj3hO4vNf/0kVrsD6uDO8LxtoUzyu 1qDHqXK/WjEQE2B8xS3J7Nao51HY0iSf5ziPLCrezCDHTr5oaQ8v1zkBUAhR1UoBczkq MR7L0C/yfy9gZfQwSzsTQKrc7KVwlPzgbgZScGhyKemJixmrhE3ht6WoboTsQvwEAp6B mjLHHdu/XfEBpAFx0uedwi5M5H01QB8pwj7Ijm45q1oGZ2mgWow3sv/Hlhc082cDdjPK dgiEd/LarGvFmynYNPtZrJ+cZzrFgPTicH7u5M0aWUYS09dRfdV5m1WzYRfK8tiud4dl bzGA== X-Gm-Message-State: AE9vXwO/EyaQBy1oLvQUYXLNINzeBNDuVexhYh1V8MXDzoGhHZRh/Iu5u8KFoIlEg6Y1oA== X-Received: by 10.28.24.73 with SMTP id 70mr9145481wmy.96.1472939616702; Sat, 03 Sep 2016 14:53:36 -0700 (PDT) Received: from [192.168.1.5] ([95.148.161.240]) by smtp.googlemail.com with ESMTPSA id pm1sm17540111wjb.40.2016.09.03.14.53.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Sep 2016 14:53:35 -0700 (PDT) To: internals@lists.php.net References: <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk> <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com> Message-ID: Date: Sat, 3 Sep 2016 22:53:35 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: rowan.collins@gmail.com (Rowan Collins) 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 according 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 you 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 to do with his RFC. Regards, -- Rowan Collins [IMSoP]