Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60263
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Jordi Boggiano <j.boggiano@seld.be>
Cc: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <4F956B74.4040104@seld.be>
References: <4F956B74.4040104@seld.be>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 23 Apr 2012 18:06:58 +0200
Message-ID: <1335197218.7272.109.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Extension versions
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2012-04-23 at 16:47 +0200, Jordi Boggiano wrote:
> As you see it goes from no version at all to proper versions, passing by
> svn revisions, dates, or a mix of all.
> 
> In Composer [1] we try to parse all that using ReflectionExtension, to
> allow people to require some specific version of an extension if they
> want. Obviously this doesn't work very well when no version or some
> random revision number is provided.
> 
> Is there any other way I overlooked to get more version info? If not,
> can this at least be improved in the future?

For PECL extensions the version number should be fine (or you can hit
the package maintainer ;-) ). For core stuff i'd propose to switch to
PHP_VERSION as version everywhere. While this can be complicated for
extensions which are maintained in both (oci8 for instance)

johannes