Re: [RFC] [Discussion] De precate PEAR and recommend Composer

On 11 October 2025 10:32:26 BST, Pierre Joye <pierre.php@gmail.com> wrote: >For the packages repositories hosted (git, ex-svn),yes, see >https://github.com/pear. The idea of the group was to be able to >take >over abandoned but widely used packages, define what licenses are >allowed and other related areas. The packages repositories not hosted >on php's repos are still where they used to be, if the service still >exists. An additional point worth noting is that all the packages in that GitHub org are published to both PEAR and Packagist. A few may not have been tested in Composer projects, but fixes are likely to be easy as long as someone's available to tag a new release - I seem to remember raising a small PR to fix some autoloading or dependency issues for something I needed. For users not ready to adopt a full Composer per-project workflow, we could recommend to use its global install mode, e.g. Replace: pear install HTML_Template_IT With: composer global install pear/html_template_it Then all that should need fixing is include paths or autoloader setup in the application. Rowan Tommins [IMSoP]