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

From: Date: Mon, 10 Jul 2006 10:21:46 +0000
Subject: Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-43309@lists.php.net to get a copy of this message
On 7/10/06, Alexey Borzov <borz_off@cs.msu.su> wrote:
Hi, Lukas Smith wrote: Lukas Smith (http://pear.php.net/user/lsmith) has commented on the proposal for RFC::Requiring E_STRICT Compatibility for New PEAR Packages. Comment: I also think it is time we nudge people a bit more strongly towards PHP5. Even if PHP5 is not the standard at this point, we need to realize that its also in our hands to change the tides. I would however leave some option open for PHP4 packages. Maybe simply increase the required +1 total to be higher than for PHP5 packages (say : 10 or 15). 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+ --Pierre --Pierre --Pierre

« previous php.pear.dev (#43309) next »