Re: Core extension versions
| From: | Marc Bennewitz | Date: | Wed, 16 Oct 2013 18:04:05 +0000 |
| Subject: | Re: Core extension versions | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-69589@lists.php.net to get a copy of this message | ||
Am 15.10.2013 18:12, schrieb Christopher Jones:
>
>
> On 10/15/13 8:45 AM, Pierre Joye wrote:
>> On Tue, Oct 15, 2013 at 5:19 PM, Michael Wallner <mike@php.net> wrote:
>>> On 15 October 2013 17:16, Anatol Belski <ab@php.net> wrote:
>>>> Hi,
>>>>
>>>> as part of the extension version check on PECL it turned out, that the
>>>> extensions in the core are almost completely out of track with their
>>>> versions, not even to talk about version macros names. That regards to
>>>> exts imported from PECL as well as to the exts never been in PECL. Here
>>>> are a few examples of zend_module_entry version strings:
>>>>
>
>>>
>>> I'd use PHP_VERSION for those extensions not explicitely managing a
>>> version.
>>
>
>>
>> PHP_VERSION-bundle
>>
>> for clarity in bug report :)
>
>
> For ext/* that do not (or no longer) have PECL releases (e.g. pdo,
> dom) I would change their versions to PHP_VERSION-bundle even if they
> currently have some rational versioning.
>
> Extensions like ext/oci8 that historically do also have PECL releases
> should manage their own version numbers
What about pecl extensions with version numbers grater than PHP_VERSION
on moving/moved to core? Don't know if this is the case somewhere.
Marc