On Mon, Jan 23, 2017 at 10:48 AM, Remi Collet <r...@fedoraproject.org> wrote:
> Le 23/01/2017 à 04:24, Rasmus Lerdorf a écrit : > > Ok, I thought perhaps the changes for just openssl-1.1 api compatibility > > would be easier to separate out, but I guess not. I did have a look at it > > and you are right, while some of the changes are trivial, others are more > > involved. Fedora 26, and I would guess any Linux distro release that > comes > > out this year, will ship with openssl-1.1 so they will not be able to run > > any version of PHP prior to 7.1. > > Fedora 26 will have openssl 1.1 and PHP 7.1. > > BTW, still a good idea to be able to build previous versions. > > Fedora also have a compat-openssl10 (version 1.0.2j for now) which allow > to build not-compatible applications. > > But as said by Rasmus, there is tons of extensions and libraries linked > against openssl, and having both versions loaded in the same process can > only be a huge mess, and raise terrible issues. > > IIRC, debian even have a patch for this. > https://anonscm.debian.org/git/pkg-php/php.git/tree/ > debian/patches/0048-Merge-OpenSSL-1.1.0-support-from-PHP-7.1-branch.patch > > Well this is just 7.1 opensssl ext which includes things that we should never add to the bug fixing release (like dropping support for 0.9.8, AEAD, pkey changes and other stuff). Not really an acceptable patch though...
