Re: Fixing bundled extension version mess
| From: | Pierre Joye | Date: | Wed, 15 Apr 2015 04:58:15 +0000 |
| Subject: | Re: Fixing bundled extension version mess | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85817@lists.php.net to get a copy of this message | ||
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