Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95837 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1957 invoked from network); 9 Sep 2016 09:19:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Sep 2016 09:19:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=mathieu@rochette.cc; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mathieu@rochette.cc; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rochette.cc designates 62.210.206.189 as permitted sender) X-PHP-List-Original-Sender: mathieu@rochette.cc X-Host-Fingerprint: 62.210.206.189 texthtml.net Received: from [62.210.206.189] ([62.210.206.189:44347] helo=texthtml.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/60-61313-BBE72D75 for ; Fri, 09 Sep 2016 05:19:56 -0400 Received: by texthtml.net (Postfix, from userid 65534) id E84C1254; Fri, 9 Sep 2016 09:19:52 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on a05d8528c5e6 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 Received: from [192.168.1.130] (stunnel_mail_1.mail_default [172.29.0.4]) (Authenticated sender: mathieu@texthtml.net) by texthtml.net (Postfix) with ESMTPA id 0951B250; Fri, 9 Sep 2016 09:19:21 +0000 (UTC) To: Tony Marston , Stanislav Malyshev , "internals@lists.php.net" References: Message-ID: <11647fac-5402-9b15-5e3e-e6c328ada7aa@rochette.cc> Date: Fri, 9 Sep 2016 11:19:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Thunderbird/50.0a2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: mathieu@rochette.cc (Mathieu Rochette) On 09/09/2016 11:01, Tony Marston wrote: > Sent: Friday, September 09, 2016 12:55 AM >> To: Tony Marston ; internals@lists.php.net >> Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle >> Hi! >> >>> There should be a rule that nothing can be deprecated unless there is a >>> viable, stable, fully functioning and fully supported alternative. I do >>> not like the way that some people simply say "I do not like this. I do >>> not use this. Nobody should be using this. Let's deprecate it" >> You can have any rules you like, but if the original author is not >> interested in the tool anymore, the only options you have are: >> >> 1. Support it yourself >> 2. Pay/beg/bribe/persuade somebody to do it for you >> 3. Failing that, use it unsupported or switch to another tool >> >> That's not only how the open source works, that's how everything works - >> try to get support for out-of-support commercial software (or >> out-of-support hardware for that matter) and see if it's any easier. >> >> So yes, it is "typical" as you note - as typical as the life can be :) >> >> That said, if the tool is useful and being used, I completely agree that >> we should make effort in keeping it supported. But we should also >> account for the possibility of that effort not being successful. > Then I suggest that you take steps to ensure that any drop-in replacement offers all the facilities of the current PEAR/PECL library. Anything less would probably annoy a largenumber of existing users. PEAR/PECL will still be available and working if the RFC passes. For most users nothing will change at all. It will only change for users installing PEAR/PECL from source along with PHP. They'll have the choice to either manually install PEAR/PECL or use something else. Installing PEAR/PECL is already documented : https://pear.php.net/manual/en/installation.getting.php. This workflow already works. what other steps should be taken ? > > -- > Tony Marston >