From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 1/4] gnupg: add license information (GPL-3.0+)
Date: Mon, 3 Oct 2016 21:01:21 +0200 [thread overview]
Message-ID: <1475521284-403-2-git-send-email-apr@cn-eng.de> (raw)
In-Reply-To: <1475521284-403-1-git-send-email-apr@cn-eng.de>
Nearly all of the code is licensed under GPL version 3 or later.
There are a few pieces which are either GPLv2+, LGPLv2.1+, LGPLv3+:
common/localename.c : LGPL-2.1+
gl/allocsa.c : GPL-2+
jnlib : LGPL-2.1+ ; LGPL-3+
All of these are only used internally (linked into gpg).
So all in all, gnupg is GPL version 3 or later.
Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
---
rules/gnupg.make | 1 +
1 file changed, 1 insertion(+)
diff --git a/rules/gnupg.make b/rules/gnupg.make
index 7f0270e..15e78eb 100644
--- a/rules/gnupg.make
+++ b/rules/gnupg.make
@@ -23,6 +23,7 @@ GNUPG_SUFFIX := tar.bz2
GNUPG_URL := ftp://ftp.gnupg.org/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
GNUPG_SOURCE := $(SRCDIR)/$(GNUPG).$(GNUPG_SUFFIX)
GNUPG_DIR := $(BUILDDIR)/$(GNUPG)
+GNUPG_LICENSE := GPL-3.0+
# ----------------------------------------------------------------------------
# Prepare
--
2.9.3
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-03 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 19:01 [ptxdist] [PATCH 0/4] gnupg, screen, squashfs-tools, zip: add license tags Andreas Pretzsch
2016-10-03 19:01 ` Andreas Pretzsch [this message]
2016-10-03 19:01 ` [ptxdist] [PATCH 2/4] screen: add license information (GPL-2.0+) Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 3/4] squashfs-tools: " Andreas Pretzsch
2016-10-03 19:01 ` [ptxdist] [PATCH 4/4] zip: add license information and license file for report generation Andreas Pretzsch
2016-10-04 13:30 ` Michael Olbrich
2016-10-04 15:50 ` Andreas Pretzsch
2016-10-04 16:40 ` [ptxdist] [PATCH v2] " Andreas Pretzsch
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=1475521284-403-2-git-send-email-apr@cn-eng.de \
--to=apr@cn-eng.de \
--cc=ptxdist@pengutronix.de \
/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