Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85827
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <014401d0778d$e5683410$b0389c30$@php.net>
References: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
	<012601d0776b$8672a250$9357e6f0$@php.net>
	<CAEPJdumD-U_TvLZxnmb62TMHSNiZCHi46peM9Ex5FhEX6eX_mA@mail.gmail.com>
	<CAEZPtU5KWhsnRNjnP71jtDjDp5Mgzmr3VK24TLy=c2esfLyMDQ@mail.gmail.com>
	<014401d0778d$e5683410$b0389c30$@php.net>
Date: Wed, 15 Apr 2015 22:39:36 +0700
Message-ID: <CAEZPtU4uro_TwtmN8fCPp6emS_jT8FLe0m=_kXii83ywCwv0HA@mail.gmail.com>
To: francois@php.net
Cc: PHP internals <internals@lists.php.net>, Benjamin Eberlei <kontakt@beberlei.de>
Content-Type: multipart/alternative; boundary=001a113fa930a6c3380513c527ec
Subject: RE: [PHP-DEV] Fixing bundled extension version mess
From: pierre.php@gmail.com (Pierre Joye)

--001a113fa930a6c3380513c527ec
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Apr 15, 2015 10:07 PM, "Fran=C3=A7ois Laupretre" <francois@php.net> wrot=
e:
>
> >De : Pierre Joye [mailto:pierre.php@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 ?
>
> - If a new PHP version is released, do we need to change the extension
version even if the code was not modified ?

Good extensions synchronize core and external releases. For example, by the
time 5.6.8 is released, the codebase matches 1.3.4 for the external
release. That will be the version exposed for the core.

The problem we have now is core extensions with senseless versions without
any external versions. Or mixed codebase, like core is a mix of external
and core specific codes which is not in any external releases. That is what
we should solve.

--001a113fa930a6c3380513c527ec--