Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
| From: | Alexey Borzov | Date: | Mon, 10 Jul 2006 10:37:51 +0000 |
| Subject: | Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43312@lists.php.net to get a copy of this message | ||
Hi,
Pierre wrote:
Yes, this makes sense. We'll give people "sitting" on some development time to push their proposals forward and if they aren't able to do it then their proposal wasn't ready in the first place.No, the whole purpose of this RFC is to discourage development of new packages for PHP4 and to encourage moving the existing packages to PHP5 versions. Adding this option defeats the purpose. There are two possibilities of a PHP4 package proposal: 1) A PEARified version of an existing library is proposed. Fortunately we have channels now and the author can distribute this library from his own site. 2) This is indeed a new package. There is no sense starting development in PHP4 if the package may stabilize only when PHP4 is completely obsolete.Let define a deadline then, I think january 2007 gives a reasonable period to anyone who still likes to propose php4 packages. After this date, only php5 (5.1+ !! ) should be accepted.
Nota Bene: If we are going to accept php5 only package, I like to go with 5.1.4+ and not 5.0++1