Re: [RFC] [Discussion] Deprecate PEAR and recommend Composer

From: Date: Fri, 10 Oct 2025 08:25:17 +0000
Subject: Re: [RFC] [Discussion] Deprecate PEAR and recommend Composer
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-128806@lists.php.net to get a copy of this message
On Thu, 9 Oct 2025 at 21:39, Christoph M. Becker wrote: > Apparently, this RFC has been withdrawn in the meantime. I would like > to know why. :) I absolutely agree with you - a discussion took place on the PHP Foundation slack. I raised a concern that it should be discussed here on the list for transparency. I am frustrated that it was not. The short version of that discussion is that PEAR is maintained by someone else; the PEAR group apparently is separate from the PHP group, as I understand it. The only thing related to PHP/internals is the fact PEAR is bundled with PHP and that the PEAR website is a subdomain pear.php.net. I withdrew the RFC because it seems this is a can of worms. On Thu, 9 Oct 2025 at 21:39, Christoph M. Becker <cmbecker69@gmx.de> wrote: > On 09.10.2025 at 12:28, James Titcumb wrote: > > > Presenting the RFC for deprecating PEAR and recommending Composer as the > > recommended > > PHP package installer: > > > > https://wiki.php.net/rfc/deprecate_pear_recommend_composer > > > > Plan to move to vote on or shortly after 24th October all being well. > > Apparently, this RFC has been withdrawn in the meantime. I would like > to know why. :) > > Christoph > > >

« previous php.internals (#128806) next »