Le 10/10/2016 à 16:29, Tomas Mraz a écrit : > On So, 2016-10-08 at 13:37 +0200, Kevin Kofler wrote: >> Tomas Mraz wrote: >>> >>> At worst if the patching of a package is highly non-trivial and the >>> upstream is not responsive we might have to drop the package from >>> Fedora. >>> >>> We do not want to keep 1.0.2 devel around as that could make it to >>> look >>> like the 1.0.2 is still fully "supported" in Fedora and there would >>> be >>> no incentive to switch to 1.1.0. Also to get any new features from >>> upstream OpenSSL we have to move to newer versions as they are >>> released >>> as the old versions get only bug fixes. >> IMHO, this is not acceptable. If the API of a library changes enough >> to >> warrant a compat package, you have to provide the -devel for the >> compat >> package as well. Dropping all the packages that don't build against >> the new >> incompatible version from Fedora is not a reasonable plan. > > We will work on porting the dependent packages to the new API. If by > some reasonable deadline there are still some packages that are not > dead by other reasons and we are unable to port them we can add -devel > to the compat package. Note though that small changes in such packages > will be needed anyway as the include files of the compat package will > have to be in non-default include directory. (If the package doesn't > use pkgconfig to find the needed CFLAGS automatically.) PHP version 7.0.x is not compatible with OpenSSL 1.1 The work is 'in progress' in PHP master (which will be 7.2) I will start to work on backporting the various upstream patches, but perhaps will be simple to first update to 7.1.x (current version is RC3) It doesn't seem possible to use a compat library (else we will very probably going to encounter issues is both library versions are used in the same process, because of the numerous libraries linked to PHP or its extensions) Remi. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
