From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] xz: LICENSE field is wrong
Date: Fri, 11 Jan 2013 15:04:16 -0800 [thread overview]
Message-ID: <1357945456-6132-1-git-send-email-sgw@linux.intel.com> (raw)
xz contains a GPLv3 m4 macro which is used at build time, this does not make
the installed or runtime items GPLv3, which is what the LICESNE field pertains
to, therefor remove it from the LICENSE field.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/recipes-extended/xz/xz_5.1.2alpha.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/xz/xz_5.1.2alpha.bb b/meta/recipes-extended/xz/xz_5.1.2alpha.bb
index 9d68720..93099b0 100644
--- a/meta/recipes-extended/xz/xz_5.1.2alpha.bb
+++ b/meta/recipes-extended/xz/xz_5.1.2alpha.bb
@@ -2,7 +2,7 @@ DESCRIPTION = "utils for managing LZMA compressed files"
HOMEPAGE = "http://tukaani.org/xz/"
SECTION = "base"
-LICENSE = "GPLv2+ & GPLv3+ & LGPLv2.1+"
+LICENSE = "GPLv2+ & LGPLv2.1+"
LIC_FILES_CHKSUM = "file://COPYING;md5=c475b6c7dca236740ace4bba553e8e1c \
file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 \
--
1.8.0.2
reply other threads:[~2013-01-11 23:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1357945456-6132-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.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