Re: [PEPr] +1 for RFC::Requiring E_STRICT Compatibility for New PEAR Packages

From: Date: Wed, 06 Sep 2006 15:54:41 +0000
Subject: Re: [PEPr] +1 for 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-43890@lists.php.net to get a copy of this message
Hi, Dan Scott wrote:
I think overloading the package name to indicate both API breaks (e.g. MDB vs. MDB2) and supported PHP versions is a mistake. Let's assume, per the example in the RFC, that package Example_Foo is created for PHP 5.1.4 E_STRICT compatibility, with Example_FooPHP4 for PHP 4 usage. When PHP 6 comes out, does Example_Foo get renamed to Example_FooPHP5 and a new package Example_Foo get released for PHP 6 compatibilty?
Please note that the RFC in question deals with acceptance of *new* packages, not with naming of new versions. To answer your question: when PHP6 finally comes out and the version of Example_Foo gets released for that, it will be named Example_Foo2.

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