Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85817
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <552DE05F.7080905@oracle.com>
References: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
	<552DE05F.7080905@oracle.com>
Date: Wed, 15 Apr 2015 11:58:15 +0700
Message-ID: <CAEZPtU5PhPZs9cYBmpvrJZJsC99Jh7VHvZBoaaoxAEBfJPtahQ@mail.gmail.com>
To: christopher jones <christopher.jones@oracle.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Fixing bundled extension version mess
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Apr 15, 2015 at 10:51 AM, christopher jones
<christopher.jones@oracle.com> wrote:
>
>
> On 4/14/15 7:21 PM, Pierre Joye wrote:
>>
>> hi,
>>
>> We tried that many times but we fail to handle the version of bundled
>> extensions.
>>
>> Along with some installer work and other integration (projects
>> dependencies management, composer or other), we need to find a way to
>> get rid of this problem.
>>
>> What do you think to simply use the PHP version number instead of some
>> outdated (most of the time) version for all bundled extensions?
>>
>> For extensions being available both bundled or externally, the
>> external versions will provide a sane version number when installed
>> (like timezone db or other).
>>
>> Doing so will make requirements management much easier by adding a
>> list of core extensions per PHP version.
>>
>> Thoughts?
>>
>> Cheers,
>>
>
> What do you mean external version?

Too many "versions" :) installed not using the core sources but
github, pecl, whatever.

> I don't have a problem with extensions having different versions
> depending how they are installed.

Cheers,
Pierre