On Wed, Apr 15, 2015 at 9:07 AM, François Laupretre <franc...@php.net> wrote:
> >De : Pierre Joye [mailto:pierre....@gmail.com] > > > > 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. > > > > Or am I missing something obvious? > > No, I just didn't understand you were just talking about extensions *not* > released outside of the core distrib. > > So, I am adapting my questions :) : > > - When we distribute the same extension code in more than one PHP release, > which version do we set for this extension ? Do we set a different version > for the same code in each release ? > I would like to see the numbers representative of changes. In that light, the version number should change, because its a new "package" even if the same code. The main I think it should change, is because many of the distros don't "include" all the core extensions (for example, installing php from apt-get in ubuntu 14.04 installs 5.5 but not with ZendOptimizer) and these extensions are separate install. As such, it would be easier to make sure you have the right things, if the versions are more specific (as per the original post in the thread). > - 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 > > - Ryan
