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

From: Date: Mon, 22 Jun 2026 07:22:23 +0000
Subject: Re: [RFC] [Discussion] Deprecate PEAR and recommend Composer
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-131445@lists.php.net to get a copy of this message
On Thu, 18 Jun 2026, at 13:08, Nick Sdot wrote: > Hey James, > > are you still planning and have time to bring this RFC to vote? After some discussion and new-to-me discoveries, I don't think there is much we can actually do, hence why I abandoned the RFC. In practice, the only association "the PEAR group" has to "the PHP group" is that the pear.php.net website points to some infrastructure hosted by "the PEAR group". It seems that "deprecating PEAR" is not really within the remit of the wider PHP community hence an RFC would not be appropriate; it's like making an RFC to deprecate Packagist... it's just not something that can be done, nor is it relevant to "the PHP group"/internals. AFAIK, the only "switch" we have available is to remove the pear.php.net DNS record, but that could potentially disrupt people still relying on pear.php.net, so is something I would NOT be in favour of. Practically, we need someone from the PEAR group to engage in discussion about the next steps, but as far as I'm aware, no-one is responding. Thanks James

« previous php.internals (#131445) next »