Le 15/04/2015 07:08, Xinchen Hui a écrit : > Hey： > > Sent from my iPhone > >> On Apr 15, 2015, at 10:21 AM, Pierre Joye <pierre....@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? > in generally, I am +1 on this > > I was also thinking of this yesterday, but the problem with opcache is: > > We already release pecl opcache with version 7.0.X > > If we now use Php version instead, then use may be confused with the versions? > > Anyway, I still +1 on this >
I'm mostly +1 on this proposal. Of course extension (like oci8) should be able to keep its version (when it is correctly managed). Yes opcache have an issue... so we probably have to keep 7.0.x until PHP 7.1 Most of the others extensions in php-src, version is just a mess. Ex: SPL version 0.2 ? really ? ;) Remi. > Thanks >> 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 > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
