gnutls: Enable p11-kit by default
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 27 lines · Richard Purdie via lists.openembedded.org
I'm not thrilled to do this but the signs are that during the lifetime of the next project release, we're going to need this and it may be best just to do it now. U-boot is the current tool that is likely to but it feels like there will be others.
We could just do this in the native case however I suspect if we're going to do it, we should do it for target and other cases as well for consistency. Most other distros are shipping with this turned on. It can still be turned off for those who don't need/want it.
Signed-off-by Richard Purdie <[email protected]>---
meta/recipes-support/gnutls/gnutls_3.8.12.bb | 2 +-1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-support/gnutls/gnutls_3.8.12.bb +0
-0@@ -30,7 +30,7 @@ SRC_URI[sha256sum] = "a7b341421bfd459acf7a374ca4af3b9e06608dcd7bd792b2bf470bea01
inherit autotools texinfo pkgconfig gettextlib_packagegtk-doc ptestmeta/recipes-support/gnutls/gnutls_3.8.12.bb +1
-1-PACKAGECONFIG ??= "libidn libtasn1 ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)}" +PACKAGECONFIG ??= "libidn libtasn1 ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)} p11-kit"
# You must also haveCONFIG_SECCOMPenabled in the kernel for
Quoted 1 line
# seccomp to work.
This breaks ptests for gnutls since it needs a recipe from meta-oe to run the p11-kit tests. It was too close to release for that.
Cheers,
Richard