From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-networking: add PACKAGECONFIG for openssl
Date: Sat, 11 May 2019 03:04:21 +0200 [thread overview]
Message-ID: <20190511010421.GA1523@jama> (raw)
In-Reply-To: <3b7d605c-ac73-6edf-7b39-598d451a4453@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3270 bytes --]
On Fri, May 10, 2019 at 04:54:57PM -0700, Khem Raj wrote:
>
>
> On 5/10/19 4:00 PM, Andre McCurdy wrote:
> > On Fri, May 10, 2019 at 3:16 PM Khem Raj <raj.khem@gmail.com> wrote:
> >>
> >> 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
>
> >
> > 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
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,
> >
> >>> - armin
> >>>
> >>> On 5/10/19 2:55 PM, Martin Jansa wrote:
> >>>> * 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 <Martin.Jansa@gmail.com>
> >>>> ---
> >>>> meta/recipes-core/glib-networking/glib-networking_2.60.1.bb | 1 +
> >>>> 1 file changed, 1 insertion(+)
> >>>>
> >>>> diff --git a/meta/recipes-core/glib-networking/glib-networking_2.60.1.bb b/meta/recipes-core/glib-networking/glib-networking_2.60.1.bb
> >>>> index 09af229d69..e2b4cffb2b 100644
> >>>> --- a/meta/recipes-core/glib-networking/glib-networking_2.60.1.bb
> >>>> +++ b/meta/recipes-core/glib-networking/glib-networking_2.60.1.bb
> >>>> @@ -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"
> >>>
> >> --
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2019-05-11 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:55 [PATCH] glib-networking: add PACKAGECONFIG for openssl Martin Jansa
2019-05-10 22:13 ` akuster808
2019-05-10 22:16 ` Khem Raj
2019-05-10 23:00 ` Andre McCurdy
2019-05-10 23:54 ` Khem Raj
2019-05-11 1:04 ` Martin Jansa [this message]
2019-05-11 1:17 ` Joshua Watt
2019-05-11 7:20 ` Adrian Bunk
2019-05-11 13:25 ` Joshua Watt
2019-05-11 6:58 ` Adrian Bunk
2019-05-14 12:02 ` Martin Jansa
2019-05-21 12:27 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190511010421.GA1523@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox