It's ok that you don't like Composer. You can find or even create a new tool which fit you needs. The reason we are talking about PEAR here, is it's bundled in the core, and no one is maintaining it. We are not saying Composer should be included into the core, at least not this thread. ------------------ Original ------------------ From: "Alice Wonder"<al...@librelamp.com>; Date: Sat, Feb 2, 2019 09:08 AM To: "internals"<internals@lists.php.net>;
Subject: Re: [PHP-DEV] Disable PEAR by default On 2/1/19 3:06 PM, Peter Kokot wrote: > Hello, > > On Fri, 1 Feb 2019 at 12:44, Joe Watkins <krak...@gmail.com> wrote: >> >> +1 >> >> On Fri, 1 Feb 2019 at 12:35, Sebastian Bergmann <sebast...@php.net> 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. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
