[PATCH] openssl: add a "openssl10" PROVIDES

[PATCH] openssl: add a "openssl10" PROVIDES

[Alexander Kanavin]

In 2.4 development cycle openssl 1.1 will replace openssl 1.0 as the
default openssl version. Openssl 1.0 will stay but will be renamed
to openssl10, and eventually it will be removed (hopefully much
sooner than the official end of support date of Dec 2019, as we do not
want an unsupported openssl version in supported Yocto releases).

There are several recipes that are not API compatible with 1.1; some
of them will eventually be fixed, but others will never be (such as Qt4).
To avoid breaking such recipes when openssl 1.1 is added to oe-core,
let's provide "openssl10" already now and change the recipes to depend
on that where necessary; Qt4 is a particularly pressing issue as it is
causing failures on the autobuilder with my work in progress
openssl 1.1 branch, and so I'm not able to see what else would fail
later in the build process.

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
 meta/recipes-connectivity/openssl/openssl.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-connectivity/openssl/openssl.inc b/meta/recipes-connectivity/openssl/openssl.inc
index 28421dab338..481a4445605 100644
--- a/meta/recipes-connectivity/openssl/openssl.inc
+++ b/meta/recipes-connectivity/openssl/openssl.inc
@@ -37,6 +37,8 @@ FILES_${PN} =+ " ${libdir}/ssl/*"
 FILES_${PN}-misc = "${libdir}/ssl/misc"
 RDEPENDS_${PN}-misc = "${@bb.utils.filter('PACKAGECONFIG', 'perl', d)}"
 
+PROVIDES += "openssl10"
+
 # Add the openssl.cnf file to the openssl-conf package.  Make the libcrypto
 # package RRECOMMENDS on this package.  This will enable the configuration
 # file to be installed for both the base openssl package and the libcrypto
-- 
2.11.0

Re: [PATCH] openssl: add a "openssl10" PROVIDES

[akuster808]

Alexander,


On 03/31/2017 02:31 AM, Alexander Kanavin wrote:
> In 2.4 development cycle openssl 1.1 will replace openssl 1.0 as the
> default openssl version. Openssl 1.0 will stay but will be renamed
> to openssl10, and eventually it will be removed (hopefully much
> sooner than the official end of support date of Dec 2019, as we do not
> want an unsupported openssl version in supported Yocto releases).
Sounds like a plan.
>
> There are several recipes that are not API compatible with 1.1; some
> of them will eventually be fixed, but others will never be (such as Qt4).
> To avoid breaking such recipes when openssl 1.1 is added to oe-core,
> let's provide "openssl10" already now and change the recipes to depend
> on that where necessary; Qt4 is a particularly pressing issue as it is
> causing failures on the autobuilder with my work in progress
> openssl 1.1 branch, and so I'm not able to see what else would fail
> later in the build process.
nice writeup.

- armin

>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
>   meta/recipes-connectivity/openssl/openssl.inc | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl.inc b/meta/recipes-connectivity/openssl/openssl.inc
> index 28421dab338..481a4445605 100644
> --- a/meta/recipes-connectivity/openssl/openssl.inc
> +++ b/meta/recipes-connectivity/openssl/openssl.inc
> @@ -37,6 +37,8 @@ FILES_${PN} =+ " ${libdir}/ssl/*"
>   FILES_${PN}-misc = "${libdir}/ssl/misc"
>   RDEPENDS_${PN}-misc = "${@bb.utils.filter('PACKAGECONFIG', 'perl', d)}"
>   
> +PROVIDES += "openssl10"
> +
>   # Add the openssl.cnf file to the openssl-conf package.  Make the libcrypto
>   # package RRECOMMENDS on this package.  This will enable the configuration
>   # file to be installed for both the base openssl package and the libcrypto