Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104004 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 17830 invoked from network); 2 Feb 2019 04:28:06 -0000 Received: from unknown (HELO librelamp.com) (45.79.96.192) by pb1.pair.com with SMTP; 2 Feb 2019 04:28:06 -0000 DKIM-Filter: OpenDKIM Filter v2.11.0 librelamp.com B9CE01146 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=librelamp.com; s=libre2019; t=1549069701; bh=PDFJg4o2QzDh1c1AjkDBw6esU99Jz4tgX5gGJqsftbQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=R5jrnvLGluLtzR5L2j4DUv+iVrzyMxWafMBjT4U4iVj73WUL/uzRbehUVW1r/J67h 3LCHixuodILlBrowmsYiMJgYi4h/x72t/C4Y7tiPPlX9r8n1wnyLGXd1DNAT2J8T7A HVJX0+Ld0KwbG90wQVoaXKH15yp8XFEl3SCrcRv0hFXuKy6bt2BybmNPl5hVkjoBes UUH3b+SR8Bz6+RMA/T2D4hOFAjrP46RnVDAwEa8bBiNZuPobjXLgnyFVmoV51FId4W MOjbdEsY0LrhPkX7ckt4ueVj6oIITKLXxspylkX37lLlUfNO+hW3M/cPp59Ht1KzgQ vdJIF6hF4ISxQ== To: internals@lists.php.net References: <7a909cd3-5d0f-8f2e-fba8-009778311bf0@php.net> Message-ID: Date: Fri, 1 Feb 2019 17:08:19 -0800 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-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Disable PEAR by default From: alice@librelamp.com (Alice Wonder) On 2/1/19 3:06 PM, Peter Kokot wrote: > Hello, > > On Fri, 1 Feb 2019 at 12:44, Joe Watkins wrote: >> >> +1 >> >> On Fri, 1 Feb 2019 at 12:35, Sebastian Bergmann wrote: >> >>> Am 01.02.2019 um 12:27 schrieb Nikita Popov: >>>> I would like to suggest that installation of PEAR is disabled by default >>> in >>>> PHP 7.4. PR: https://github.com/php/php-src/pull/3781 >>> >>> +1 > > Thank you Nikita for the pull request for this. With all the respect > to PEAR project and people behind it, maybe the PEAR itself should be > added to some sort of recognition page in the manual for their > involvement and work on the first installer of PHP code and initial > move into code reuse, open source PHP libraries, and all that. As time > went forward, Composer took over the role of such installer in PHP > community. I do not like composer. A problem I have encountered, a project specifies a version for a dependency. That version has vulnerability, developer fixed it in newer release, but composer keeps pulling in the older version because that is what composer provides. And it can be the dependency of a dependency of a dependency. I do not like Composer. Adding a "recognition page" while cutting PEAR off also seems, well, slimy.