From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/nettle: clarify license info
Date: Fri, 31 Jul 2026 14:05:16 +0200 [thread overview]
Message-ID: <20260731120516.3490-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260720170437.133823-3-fiona.klute@gmx.de>
In reply of:
> The Nettle manual (nettle.html in the source archive) states:
>
> > Nettle is dual licenced under the GNU General Public License version
> > 2 or later, and the GNU Lesser General Public License version 3 or
> > later. When using Nettle, you must comply fully with all conditions
> > of at least one of these licenses. [...]
>
> This means "or" is the correct description. Ellipsis covers a note
> that a few files are licensed more permissively.
>
> Signed-off-by: Fiona Klute (Othermo GmbH) <fiona.klute@gmx.de>
Applied to 2025.02.x & 2026.05.x. Thanks
> ---
> package/nettle/nettle.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/nettle/nettle.mk b/package/nettle/nettle.mk
> index 93c638a4cd..dbbd60622d 100644
> --- a/package/nettle/nettle.mk
> +++ b/package/nettle/nettle.mk
> @@ -8,7 +8,7 @@ NETTLE_VERSION = 3.10.2
> NETTLE_SITE = $(BR2_GNU_MIRROR)/nettle
> NETTLE_DEPENDENCIES = host-m4 gmp
> NETTLE_INSTALL_STAGING = YES
> -NETTLE_LICENSE = Dual GPL-2.0+/LGPL-3.0+
> +NETTLE_LICENSE = GPL-2.0+ or LGPL-3.0+
> NETTLE_LICENSE_FILES = COPYING.LESSERv3 COPYINGv2
> NETTLE_CPE_ID_VALID = YES
> # don't include openssl support for (unused) examples as it has problems
> --
> 2.53.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-31 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 17:04 [Buildroot] [PATCH 1/4] package/python-paho-mqtt: clarify license information Fiona Klute via buildroot
2026-07-20 17:04 ` [Buildroot] [PATCH 2/4] package/dbus-broker: " Fiona Klute via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot
2026-07-20 17:04 ` [Buildroot] [PATCH 3/4] package/nettle: clarify license info Fiona Klute via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot [this message]
2026-07-20 17:04 ` [Buildroot] [PATCH 4/4] package/busybox: use SPDX license identifier for bzip2 license Fiona Klute via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot
2026-07-20 20:16 ` [Buildroot] [PATCH 1/4] package/python-paho-mqtt: clarify license information Julien Olivain via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot
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=20260731120516.3490-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=thomas.perale@mind.be \
/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