Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128822
Date: Mon, 13 Oct 2025 20:01:15 +0200 (CEST)
To: Jakub Zelenka <bukka@php.net>
cc: Brent Roose <brent.roose@jetbrains.com>, 
    PHP Internals List <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Deprecate PEAR and recommend
 Composer
In-Reply-To: <CAEKnhAGEzupa25BbWy60h_EKrM9e0txm2Tao+vZON=Ob=ce-Bw@mail.gmail.com>
Message-ID: <c1451dfa-c38a-f421-66c9-aa51b949aeb9@php.net>
References: <CAOD_yv0k=1nBq6LOR9w2pNXHnjtPL5NtBV=SLRsKjpVCK1dFug@mail.gmail.com> <fdf1d284-27bf-4bb2-924e-21fa82673c6f@gmx.de> <CAOD_yv2Sga6P1N-Uu2w-nyyY-XMvytWy-_r1v=xZpygQ_67iRQ@mail.gmail.com> <CAEZPtU6NJfxjckrpikVfmFcJ2OyhhKg3YJdqTkpvPaU_uMeyGg@mail.gmail.com>
 <CAEKnhAEsGS+k7Mg4Z1z-fbWh4hsAbkpgTxsdJEYaG7N1+F=Ddg@mail.gmail.com> <CANSNCr1paQGq3Vg0MKsNkZagtRweGpQuu9jy-bpnot_=RbLv-g@mail.gmail.com> <CAEKnhAGEzupa25BbWy60h_EKrM9e0txm2Tao+vZON=Ob=ce-Bw@mail.gmail.com>
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-886108392-1760378476=:167098"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-886108392-1760378476=:167098
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Fri, 10 Oct 2025, Jakub Zelenka wrote:

> Hi,
>=20
> On Fri, Oct 10, 2025 at 2:44=E2=80=AFPM Brent Roose <brent.roose@jetbrain=
s.com>
> wrote:
>=20
> > The only thing related to PHP/internals is the fact PEAR is bundled wit=
h
> >> PHP and that the PEAR website is a subdomain pear.php.net.
> >>
> >
> > In my opinion, this is sufficient reason to have an RFC for it. A quick
> > search through the RFCs showed a handful of website-related ones:
> >
> > - https://wiki.php.net/rfc/deprecate-pear-include-composer
> > - https://wiki.php.net/rfc/global_login
> > - https://wiki.php.net/rfc/phpnet-analytics
> >
> > Then there's the fact that Pear comes bundled with PHP, even more of an
> > argument that internals have at least something to say about it. Severa=
l
> > RFCs have addressed bundling/unbundling third party plugins before. Aga=
in,
> > a quick search:
> >
> > - https://wiki.php.net/rfc/unbundle_imap_pspell_oci8
> > - https://wiki.php.net/rfc/unbundle_xmlprc
> > - https://wiki.php.net/rfc/deprecate-and-remove-ext-wddx
> > - https://wiki.php.net/rfc/unbundle_recode
> >
> > To me, and I believe to a significant part of the PHP community, what's
> > most important is for PHP to acknowledge that composer is its de-facto
> > standard package manager. This doesn't mean composer cannot operate
> > independently anymore, but an endorsement would make a lot of sense.
> >
>=20
> Removing PEAR/PECL from php-src is absolutely fine and such RFC should=20
> be done. As I mentioned, we could also discuss removal from the=20
> php.net domain (move it to the separate domain from pear.php.net).=20
> That's what we control and can do.

I think these would be my primary actions too:

- unbundle pear/pecl from PHP alltogether
- not have pear.php.net on the php.net domain.

The latter is because we have no access, and I have no idea what OS it=20
runs, how it is set up, and whether it even received package and OS=20
updates in the last decade.

Then somebody else can decide later whether they want to abandon PEAR=20
(and it's new hosted website).

cheers,
Derick

--=20
https://derickrethans.nl | https://xdebug.org | https://dram.io

Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo=
rt

mastodon: @derickr@phpc.social @xdebug@phpc.social
--8323329-886108392-1760378476=:167098--