glib-networking: add PACKAGECONFIG for openssl
PATCH 1/1 glib-networking: add PACKAGECONFIG for openssl
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'
* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend
* add an option to replace gnutls with openssl
--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1 -0
@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls" PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"
Signature · 1 line
2.17.1
should we change the default to openssl ?
- armin
Quoted 25 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls" PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"
Quoted 2 lines · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Quoted 29 lines
- armin
Quoted 25 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls" PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"
Quoted 5 lines · Khem Raj
Quoted 1 line · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Isn't one of the goals for OE 2.8 to replace dependencies on [L]GPLv3 components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
https://github.com/GNOME/glib-networking/blob/master/NEWS
Quoted 34 lines
Quoted 23 lines
- armin
Quoted 20 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls"Quoted 6 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a · line 21
Quoted 5 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 10 lines · Andre McCurdy
Quoted 5 lines · Khem Raj
Quoted 1 line · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Isn't one of the goals for OE 2.8 to replace dependencies on [L]GPLv3 components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
Is that stated somewhere ? while I like the goal probably I missed the memo, my suggestion was just to give openssl backend some time to mature since its relatively new, and maybe give it some soak time
Quoted 41 lines
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
https://github.com/GNOME/glib-networking/blob/master/NEWS
Quoted 34 lines
Quoted 23 lines
- armin
Quoted 20 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls"Quoted 6 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a · line 21
Quoted 5 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 10 lines · Khem Raj
Quoted 7 lines · Andre McCurdy
Quoted 5 lines · Khem Raj
Quoted 1 line · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Quoted 14 lines
Quoted 3 lines
Isn't one of the goals for OE 2.8 to replace dependencies on [L]GPLv3 components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
Is that stated somewhere ? while I like the goal probably I missed the memo, my suggestion was just to give openssl backend some time to mature since its relatively new, and maybe give it some soak time
Quoted 6 lines
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
I don't have strong opinion either way.
I didn't want to change the default, because my only motivation was the license issue with the newer gnutls, with the PACKAGECONFIG available it's easy to change the TLS backend and that's all I need.
Will send v2 if there is some consensus from glib-networking users that it should be changed and someone provides me the reasoning for the commit message.
Cheers,
Quoted 35 lines
Quoted 35 lines
Quoted 35 lines
Quoted 24 lines
- armin
Quoted 20 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls' ['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled. Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a PACKAGECONFIG ??= "gnutls"Quoted 6 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a · line 21
Quoted 5 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls" +PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl" PACKAGECONFIG[libproxy] = "-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy" EXTRA_OEMESON = "-Dgnome_proxy=disabled"--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 28 lines · Martin Jansa
Quoted 10 lines · Khem Raj
Quoted 7 lines · Andre McCurdy
Quoted 5 lines · Khem Raj
Quoted 1 line · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Quoted 14 lines
Quoted 3 lines
Isn't one of the goals for OE 2.8 to replace dependencies on [L]GPLv3 components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
Is that stated somewhere ? while I like the goal probably I missed the memo, my suggestion was just to give openssl backend some time to mature since its relatively new, and maybe give it some soak time
Quoted 6 lines
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
I don't have strong opinion either way.
Quoted 8 lines
I didn't want to change the default, because my only motivation was the license issue with the newer gnutls, with the PACKAGECONFIG available it's easy to change the TLS backend and that's all I need.
Will send v2 if there is some consensus from glib-networking users that it should be changed and someone provides me the reasoning for the commit message.
FWIW, moving away from GPLv3 and/or meta-gplv2 has been discussed in the 2.8 planning meetings:
https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/edit?usp=drivesdk
Not that it needs to be done right now. It is nice to at least have the option.
Quoted 56 lines
Cheers,
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
- armin
Quoted 1 line · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of
glib-networking:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
meson.build:74:0: ERROR: Invalid version of dependency, need
'gnutls' ['>= 3.4.6'] found '3.3.30'
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backendsenabled. Please enable at least one TLS backend
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1+
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Review
Quoted 3 lines
1 file changed, 1 insertion(+)(quoted diff) +0
-0glib-networking_2.60.1.bb b/meta/recipes-core/glib-networking/ glib-networking_2.60.1.bb
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] =
Quoted 4 lines
index
09af229d69..e2b4cffb2b100644meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] ="
d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0aQuoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a
Quoted 3 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0PACKAGECONFIG ??= "gnutls" PACKAGECONFIG[gnutls] ="-Dgnutls=enabled,-Dgnutls=disabled,gnutls"
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = · line 18
Quoted 1 line
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +1
-0+PACKAGECONFIG[openssl] ="-Dopenssl=enabled,-Dopenssl=disabled,openssl"
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = · line 19
Quoted 1 line
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0PACKAGECONFIG[libproxy] ="-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy"
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb SRC_URI[archive.sha256sum] = "d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a · line 21
Quoted 2 lines
meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0EXTRA_OEMESON = "-Dgnome_proxy=disabled"--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 39 lines · Joshua Watt
Quoted 28 lines · Martin Jansa
Quoted 10 lines · Khem Raj
Quoted 7 lines · Andre McCurdy
Quoted 5 lines · Khem Raj
Quoted 1 line · On 5/10/19 3:13 PM, akuster808 wrote:
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Quoted 14 lines
Quoted 3 lines
Isn't one of the goals for OE 2.8 to replace dependencies on [L]GPLv3 components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
Is that stated somewhere ? while I like the goal probably I missed the memo, my suggestion was just to give openssl backend some time to mature since its relatively new, and maybe give it some soak time
Quoted 6 lines
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
I don't have strong opinion either way.
Quoted 8 lines
I didn't want to change the default, because my only motivation was the license issue with the newer gnutls, with the PACKAGECONFIG available it's easy to change the TLS backend and that's all I need.
Will send v2 if there is some consensus from glib-networking users that it should be changed and someone provides me the reasoning for the commit message.
Quoted 6 lines
FWIW, moving away from GPLv3 and/or meta-gplv2 has been discussed in the 2.8 planning meetings:
https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/edit?usp=drivesdkNot that it needs to be done right now. It is nice to at least have the option.
It doesn't read as if "replace dependencies on [L]GPLv3 components" or "moving away from GPLv3" would charcterize it correctly.
It says to create a *configuration* for the small subset of Yocto users who do not want to have GPLv3 code on their target.
For these users it is clear that they want to use openssl if they use glib-networking,[1] and that they want to stick with busybox applets instead of bash and all the GNU utilities.
For everyone else nothing has to change.
cu
Adrian
[1] Which BTW creates its own licence headaches due to OpenSSL having a GPL-incompatible licence.
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 56 lines · Adrian Bunk
Quoted 1 line · Joshua Watt
On Fri, May 10, 2019, 8:04 PM Martin Jansa <[email protected]>
Quoted 6 lines · wrote:
Quoted 6 lines · Khem Raj
Quoted 4 lines · Andre McCurdy
Quoted 1 line
On Fri, May 10, 2019 at 3:16 PM Khem Raj <[email protected]>
Quoted 7 lines · wrote:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines · On 5/10/19 3:13 PM, akuster808 wrote:
Quoted 1 line
should we change the default to openssl ?
I dont think so. Since newer versions of gnuTLS works okay.
Isn't one of the goals for OE 2.8 to replace dependencies on
[L]GPLv3
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
components with non-[L]GPLv3 alternatives so that meta-gplv2 can be deprecated? This would seem to fit that goal exactly.
Is that stated somewhere ? while I like the goal probably I missed
the
Quoted 1 line
Quoted 1 line
Quoted 1 line
memo, my suggestion was just to give openssl backend some time to
mature
Quoted 15 lines
Quoted 15 lines
Quoted 8 lines
since its relatively new, and maybe give it some soak time
Quoted 6 lines
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
I don't have strong opinion either way.
I didn't want to change the default, because my only motivation was the license issue with the newer gnutls, with the PACKAGECONFIG available it's easy to change the TLS backend and that's all I need.
Quoted 8 lines
Quoted 4 lines
Will send v2 if there is some consensus from glib-networking users that it should be changed and someone provides me the reasoning for the commit message.
FWIW, moving away from GPLv3 and/or meta-gplv2 has been discussed in the 2.8 planning meetings:
https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/edit?usp=drivesdk
Quoted 3 lines
Not that it needs to be done right now. It is nice to at least have the option.
It doesn't read as if "replace dependencies on [L]GPLv3 components" or "moving away from GPLv3" would charcterize it correctly.
Quoted 7 lines
It says to create a *configuration* for the small subset of Yocto users who do not want to have GPLv3 code on their target.
For these users it is clear that they want to use openssl if they use glib-networking,[1] and that they want to stick with busybox applets instead of bash and all the GNU utilities.
Right, I was a little too strong there; I didn't mean to imply that anyone is proposing to completely remove GPLv3, just provide alternatives that aren't meta-gplv2.
Quoted 16 lines
For everyone else nothing has to change.
cu
Adrian[1] Which BTW creates its own licence headaches due to OpenSSL having a GPL-incompatible licence.
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Quoted 6 lines · Andre McCurdy
...
It wasn't possible to build glib-networking with openssl until very recently but now that it's supported upstream I think we should switch.
This states clearly that we should not switch:
This is the first stable release featuring the new OpenSSL backend. Please be advised that this new backend is still experimental and known to not work on some systems, including Debian. Linux distributions are encouraged to stick to the default build options, where OpenSSL is not yet enabled.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedThanks all, I think the discussion made it clear that we shouldn't change the default yet.
Makes it easier for me as I'll need this PACKAGECONFIG backported to warrior as well (and we shouldn't change the default there for sure).
RP: please take this for some next master-next.
Quoted 35 lines · Martin Jansa
* gnutls from meta-gplv2 isn't new enough for this version of glib-networking:
meson.build:74:0: ERROR: Invalid version of dependency, need 'gnutls'
['>= 3.4.6'] found '3.3.30'* disabling gnutls PACKAGECONFIG isn't an option either:
meson.build:131:2: ERROR: Problem encountered: No TLS backends enabled.
Please enable at least one TLS backend* add an option to replace gnutls with openssl
Signed-off-by Martin Jansa <[email protected]>--- meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 + 1 file changed, 1 insertion(+)meta/recipes-core/glib-networking/glib-networking_2.60.1.bb +0
-0@@ -15,6 +15,7 @@ SRC_URI[archive.sha256sum] ="
d71c6b2faa5ac29100314f08a1be020a2afd0291f025614c0a
PACKAGECONFIG ??= "gnutls"PACKAGECONFIG[gnutls] = "-Dgnutls=enabled,-Dgnutls=disabled,gnutls"
+PACKAGECONFIG[openssl] = "-Dopenssl=enabled,-Dopenssl=disabled,openssl"
PACKAGECONFIG[libproxy] =
"-Dlibproxy=enabled,-Dlibproxy=disabled,libproxy"
EXTRA_OEMESON= "-Dgnome_proxy=disabled"
--
2.17.1
Quoted 7 lines · Martin Jansa
Thanks all, I think the discussion made it clear that we shouldn't change the default yet.
Makes it easier for me as I'll need this PACKAGECONFIG backported to warrior as well (and we shouldn't change the default there for sure).
RP: please take this for some next master-next.
Ping?