Re: Fixing bundled extension version mess
| From: | Kris Craig | Date: | Wed, 15 Apr 2015 02:29:55 +0000 |
| Subject: | Re: Fixing bundled extension version mess | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85815@lists.php.net to get a copy of this message | ||
On Tue, Apr 14, 2015 at 7:21 PM, Pierre Joye <pierre.php@gmail.com> 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,
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Big +1 for this! It would certainly make things less confusing for many
people.
--Kris