Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104338
MIME-Version: 1.0
References: <CAF+90c-B=xU9phGNxcRvZE+2c1RkKvsiDXU0qzWJdU_U3Tskag@mail.gmail.com>
In-Reply-To: <CAF+90c-B=xU9phGNxcRvZE+2c1RkKvsiDXU0qzWJdU_U3Tskag@mail.gmail.com>
Date: Mon, 11 Feb 2019 11:16:13 +0100
Message-ID: <CAF+90c_jgZS58qygv_FuqHNRmOMQMMnMPYReebgEo_nTF4U4yg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000053dd7305819b9a05"
Subject: Re: Disable PEAR by default
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000053dd7305819b9a05
Content-Type: text/plain; charset="UTF-8"

On Fri, Feb 1, 2019 at 12:27 PM Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> 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
>
> I think the reasons for this should be obvious. It's not really the recent
> security breach itself, but rather the underlying issue that PEAR simply
> isn't actively maintained anymore.
>
> Currently PEAR is broken on master due to the removal of each(), which was
> deprecated in PHP 7.2. Apparently, since that time nobody noticed that PEAR
> is throwing deprecation errors, or at least nobody bothered to fix them.
> (I've submitted https://github.com/pear/Console_Getopt/pull/3 to fix at
> least this particular issue.)
>
> It's somewhat unfortunate that PEAR and PECL are coupled projects, but I
> don't think that should prevent us from changing this default.
>
> Regards,
> Nikita
>

I've gone ahead and merged this change. PEAR is no longer installed by
default, instead --with-pear must be specified. Additionally the option
generates a deprecation warning during ./configure now.

Nikita

--00000000000053dd7305819b9a05--