Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104025 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71948 invoked from network); 2 Feb 2019 18:52:06 -0000 Received: from unknown (HELO mail4.serversure.net) (185.153.204.204) by pb1.pair.com with SMTP; 2 Feb 2019 18:52:06 -0000 Received: (qmail 28535 invoked by uid 89); 2 Feb 2019 15:32:30 -0000 Received: by simscan 1.3.1 ppid: 28529, pid: 28532, t: 0.0381s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@lsces.co.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 2 Feb 2019 15:32:30 -0000 To: internals@lists.php.net References: <7a909cd3-5d0f-8f2e-fba8-009778311bf0@php.net> <77f41814-bb27-bdf0-44d3-d59b64de7d45@librelamp.com> Message-ID: <71208bf6-eded-ea07-6246-2cb830f0cd05@lsces.co.uk> Date: Sat, 2 Feb 2019 15:32:30 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Disable PEAR by default From: lester@lsces.co.uk (Lester Caine) On 02/02/2019 14:28, Peter Kokot wrote: > About PECL, then I assume we keep it as is for this period also. > Unclear, required to install PEAR to be able to run the pecl command, > and optionally moving this part elsewhere out of the PHP. Specially, > to package maintainers (Linux distros), another repository/project out > of the scope of the PHP internals etc. I have to admit that since nowadays I only install PHP via OpenSUSE, what is in core is not actually relevant to me directly since even the packages that HAVE been dropped from core are still fully supported! BUT many of the people I am supporting are only using Windows so it is nice that there is a tidy path for 'package management'. That has included adding PECL packages in recent years and which was still working nicely. Those people have not upgraded from PHP5 for many reasons and having to address additional changes to a stable windows base is just more blockers to bringing the over 70% of sites that are still on PHP5 forward to PHP7. Especially if other moves make Windows a second class citizen? -- Lester Caine - G8HFL ----------------------------- Contact - https://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - https://lsces.co.uk EnquirySolve - https://enquirysolve.com/ Model Engineers Digital Workshop - https://medw.co.uk Rainbow Digital Media - https://rainbowdigitalmedia.co.uk