Again, take #3, ext released in and outiside the core will use the external version number everywhere. Like oci, zip and other well managed versions. The stupid think like 0.1 since 8 years will use the php version. That is all.
Installer can easily knows which uses what. Or am I missing something obvious? On Apr 15, 2015 8:19 PM, "Benjamin Eberlei" <kont...@beberlei.de> wrote: > > On Wed, Apr 15, 2015 at 1:01 PM, François Laupretre <franc...@php.net> > wrote: > >> > De : Pierre Joye [mailto:pierre....@gmail.com] >> > >> > What do you think to simply use the PHP version number instead of some >> > outdated (most of the time) version for all bundled extensions? >> >> As the idea is that extensions available externally are supposed to >> change more often than the bundled version, why wouldn't we add a fourth >> number to their version ? By definition, version X.Y.Z.0 would correspond >> to the version distributed with PHP X.Y.Z. >> > > But its not clear if this makes sense. if you have extension "foo" in php > 7.0.1 and 7.0.2 and you want to provide an override via pecl, would you > need to release 7.0.1.1 and 7.0.2.1? That doesnt make sense imho. > > Its either PHP Version == Ext Version or Ext has its own version. By > default it should be the first, but some maintainers could deviate if they > wish. > >> >> Also : >> >> - When we distribute the same extension code with PHP 5.4, 5.5, and 5.6, >> what is the version we set for this code in pecl ? Will we have to create 3 >> branches, just for versions ? >> >> - If a new PHP version is released, do we need to change the extension >> version even if the code was not modified ? >> >> Regards >> >> François >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> >
