From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] gnutls: update legal info
Date: Tue, 5 Jul 2016 00:13:45 +0200 [thread overview]
Message-ID: <20160705001345.3cbcd8b3@free-electrons.com> (raw)
In-Reply-To: <20160704153950.GB3549@free.fr>
Hello,
On Mon, 4 Jul 2016 17:39:50 +0200, Yann E. MORIN wrote:
> On 2016-07-04 18:16 +0530, Rahul Bedarkar spake thusly:
> > GnuTLS core library is licensed under LGPLv2.1+ while gnutls-openssl
> > library is licensed under GPLv3+. Annotate the license with components.
>
> What do you call "core library" and "gnutls-openssl library"?
This is explained in the README file:
"""
Since GnuTLS version 3.1.10, the core library has been released under
the GNU Lesser General Public License (LGPL) version 2.1 or later.
Note, however, that version 6.0.0 and later of the gmplib library used
by GnuTLS are distributed under a LGPLv3+ or GPLv2+ dual license, and
as such binaries of this library need to adhere to either LGPLv3+ or
GPLv2+ license.
The GNU LGPL applies to the main GnuTLS library, while the
included applications as well as gnutls-openssl
library are under the GNU GPL version 3. The gnutls library is
located in the lib/ and libdane/ directories, while the applications
in src/ and, the gnutls-openssl library is at extra/.
"""
>
> Do you consider libdane to be that "gnutls-openssl library" you talk
> about?
No, see above. libdane is part of the "core library".
> I've looked at the source, and libdane is (at least partially) LGPLv3:
>
> libdane/errors.c:
> [--SNIP--]
> * libdane is free software; you can redistribute it and/or
> * modify it under the terms of the GNU Lesser General Public License
> * as published by the Free Software Foundation; either version 3 of
> * the License, or (at your option) any later version.
> [--SNIP--]
This seems to be a bug, which I've reported upstream at
https://gitlab.com/gnutls/gnutls/issues/109.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-04 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 12:46 [Buildroot] [PATCH 1/6] gnutls: update legal info Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 2/6] libuci: " Rahul Bedarkar
2016-07-04 15:46 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 3/6] dbus: " Rahul Bedarkar
2016-07-04 12:46 ` [Buildroot] [PATCH 4/6] iw: correct license name Rahul Bedarkar
2016-07-04 15:56 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 5/6] gmp: correct legal info Rahul Bedarkar
2016-07-04 16:07 ` Yann E. MORIN
2016-07-04 12:46 ` [Buildroot] [PATCH 6/6] alsa-lib: update " Rahul Bedarkar
2016-07-04 16:14 ` Yann E. MORIN
2016-07-05 7:15 ` Thomas Petazzoni
2016-07-04 15:39 ` [Buildroot] [PATCH 1/6] gnutls: " Yann E. MORIN
2016-07-04 22:13 ` Thomas Petazzoni [this message]
2016-07-04 22:14 ` Thomas Petazzoni
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=20160705001345.3cbcd8b3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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