Re: move PEAR to PHP 5-only?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Beaver wrote: > Hi all, > > How do PEAR developers feel about moving PEAR 1.5 to PHP5-only? > > PEAR 1.4.2 will be out shortly, with all pecl issues fixed, which works > in PHP 4.x just fine. > - -1. As discussed, this is a BC break - or at least, I consider it a BC break. *No* php code can be E_STRICT clean and run under PHP 4 and 5, so any efforts in that direction break BC with PEAR 1.x. The logical thing to do if people want E_STRICT PEAR code is to start working on a PHP 5-only PEAR 2. PEAR 1.4.x would be put into bugfix-only maintainance mode, unless someone steps up specifically to maintain it. I'm not convinced that it would take a year or more to make that happen, since so much of what PEAR originally did has been integrated into PHP itself. I think the focus should be on PEAR as a distribution system vs. PEAR as a PHP OOP helper, an idea which seems to have a few other developers behind it. I'd basically like to see: - - PEAR 1.4.x stabilized and put into maintainance mode. - - Start work on PEAR 2.x, PHP 5 (or 6) only. - Ditch package.xml v1 support, and any other 1.x legacy stuff. - Focus on the installer. The current pear command has a ton of stuff most people aren't going to need (such as the developer tools). I'd like to see these split out, or perhaps a modular approach where sets of commands could be added by installing PEAR-cli-developer. - Focus on CS and adherence to PEAR standards & practices. I'd be glad to write up some additional thoughts and create a PECl proposal. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDQav/xuUdPD6j2IMRAnDjAKCEGzyIKD1AiQ8wiFDNvWeWG+blBgCfW4kR ZY7WM7OFvBMOEmNYiYp0Bqc= =H7vq -----END PGP SIGNATURE-----