From: Adrian Bunk <bunk@stusta.de>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-networking: add PACKAGECONFIG for openssl
Date: Sat, 11 May 2019 10:20:48 +0300 [thread overview]
Message-ID: <20190511072048.GB24494@localhost> (raw)
In-Reply-To: <CAJdd5GYVfHO8Hs21P0Ohun12nEEqcgwBeWdYtsUPdtLGLi6MXQ@mail.gmail.com>
On Fri, May 10, 2019 at 08:17:50PM -0500, Joshua Watt wrote:
> On Fri, May 10, 2019, 8:04 PM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> > 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.
> >
>
> 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.
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.
--
"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
next prev parent reply other threads:[~2019-05-11 7:20 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
2019-05-11 1:17 ` Joshua Watt
2019-05-11 7:20 ` Adrian Bunk [this message]
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=20190511072048.GB24494@localhost \
--to=bunk@stusta.de \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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