Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85824
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEPJdumD-U_TvLZxnmb62TMHSNiZCHi46peM9Ex5FhEX6eX_mA@mail.gmail.com>
References: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
	<012601d0776b$8672a250$9357e6f0$@php.net>
	<CAEPJdumD-U_TvLZxnmb62TMHSNiZCHi46peM9Ex5FhEX6eX_mA@mail.gmail.com>
Date: Wed, 15 Apr 2015 21:04:18 +0700
Message-ID: <CAEZPtU5KWhsnRNjnP71jtDjDp5Mgzmr3VK24TLy=c2esfLyMDQ@mail.gmail.com>
To: Benjamin Eberlei <kontakt@beberlei.de>
Cc: PHP internals <internals@lists.php.net>, francois@php.net
Content-Type: multipart/alternative; boundary=001a11c006b0c22a0d0513c3d235
Subject: Re: [PHP-DEV] Fixing bundled extension version mess
From: pierre.php@gmail.com (Pierre Joye)

--001a11c006b0c22a0d0513c3d235
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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" <kontakt@beberlei.de> wrote:

>
> On Wed, Apr 15, 2015 at 1:01 PM, Fran=C3=A7ois Laupretre <francois@php.ne=
t>
> wrote:
>
>> > De : Pierre Joye [mailto:pierre.php@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 correspon=
d
>> 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 =3D=3D Ext Version or Ext has its own version. By
> default it should be the first, but some maintainers could deviate if the=
y
> 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 creat=
e 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=C3=A7ois
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>

--001a11c006b0c22a0d0513c3d235--