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

On 7/10/06, Lukas Smith <lsmith@php.net> wrote:

Alexey Borzov wrote:

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. Not sure if that is really a good idea. The 2 versions still need to be maintained. Beyond the interest of the given developer. Anyways if we allow PHP4 packages upto a given point, there is nothing from stopping them proposing a PHP4 variant of their package upto that point.

I agree here, the risk to make the RFC pointless is very high. I was not a fan of "forcing" people to update to php5. In the past weeks (and outside the pear FUDs about exception and other topics ;), I changed my mind. We can wait (always too long) or give the impulsion to boost php5 usage in PEAR. I think this RFC can give the good signal and force the slowest developer to update. --Pierre