From: Leo Famulari <leo@famulari.name>
To: Antero Mejr <antero@mailbox.org>
Cc: 61950@debbugs.gnu.org, me@tobias.gr
Subject: [bug#61950] [PATCH] gnu: nettle-2: Add lgpl3+ to licenses.
Date: Mon, 6 Mar 2023 16:20:12 -0500 [thread overview]
Message-ID: <ZAZZDFPi0ugOpEid@jasmine.lan> (raw)
In-Reply-To: <20230306185603.9936-1-antero@mailbox.org>
On Mon, Mar 06, 2023 at 06:56:03PM +0000, Antero Mejr wrote:
> - (license gpl2+)))
> + (license (list lgpl3+ ;dual licensed, see COPYING.LIB/COPYING.LESSERv3 file
> + gpl2+)))) ;COPYING, renamed to COPYINGv2 in later versions
I don't understand the comment.
What is 'COPYING.LIB'? That file doesn't exist in the source code of
nettle 3.7.3.
Are users free to choose a license? Do they apply to different use
cases? Where do the Nettle authors explain the licensing?
prev parent reply other threads:[~2023-03-06 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 4:14 [bug#61950] [PATCH] lint: Add 'copyleft' checker Antero Mejr via Guix-patches via
2023-03-04 4:22 ` [bug#61950] [PATCH 1/3] gnu: libsndfile: Correct license Antero Mejr via Guix-patches via
2023-03-04 4:22 ` [bug#61950] [PATCH 2/3] gnu: libcap: Add bsd-3 license Antero Mejr via Guix-patches via
2023-03-06 16:49 ` Leo Famulari
2023-03-04 4:22 ` [bug#61950] [PATCH 3/3] gnu: nettle-2: Add lgpl3+ to licenses Antero Mejr via Guix-patches via
2023-03-06 16:50 ` Leo Famulari
2023-03-06 16:49 ` [bug#61950] [PATCH 1/3] gnu: libsndfile: Correct license Leo Famulari
2023-03-06 15:53 ` [bug#61950] [PATCH] lint: Add 'copyleft' checker Ludovic Courtès
2023-03-06 16:21 ` Antero Mejr via Guix-patches via
2023-03-06 22:38 ` Ludovic Courtès
2023-03-22 2:48 ` Maxim Cournoyer
2023-03-22 21:56 ` Antero Mejr via Guix-patches via
2023-03-23 2:48 ` bug#61950: " Maxim Cournoyer
2023-03-06 16:45 ` [bug#61950] " Leo Famulari
2023-03-06 18:56 ` [bug#61950] [PATCH] gnu: nettle-2: Add lgpl3+ to licenses Antero Mejr via Guix-patches via
2023-03-06 21:20 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAZZDFPi0ugOpEid@jasmine.lan \
--to=leo@famulari.name \
--cc=61950@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).