Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages

Hi, Philippe Jausions wrote:

I don't really see the point of this RFC.

The point of this RFC is discouraging the development of new packages for PHP4 and encouraging said development for PHP5.

Packages make their way into PEAR because people wrote them and wanted to share them with the rest of the world. Sometimes these packages *had* to be written in PHP4. And some other users may need such a version as well.

Sometimes these packages had to be written in PHP3, yet PEAR has no PHP3 packages. This is a question of policy...

I understand the need to move forward to PHP5, but if people can't use a PHP5 version of a package and a PHP4 is available, the RFC shouldn't forbid the PH4 package to make it into PEAR. The RFC should state that new packages must provide a PHP5 E_STRICT version, but not restrict to that version only.

I sincerely doubt that people would write two versions of packages but if this ever happens... OK, I'll add this idea to the RFC.

The dependency on E_STRICT packages will slow development if nothing is done first to up some major existing packages.

Yes, I'm aware of the fact. But not enforcing this rule has some problems, too, see my response to Justin.