Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.180 as permitted sender)
MIME-Version: 1.0
Date: Wed, 15 Apr 2015 09:21:46 +0700
Message-ID: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Fixing bundled extension version mess
From: pierre.php@gmail.com (Pierre Joye)

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,
-- 
Pierre

@pierrejoye | http://www.libgd.org