From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Cc: Nikolay Papenkov <n.papenkov@inango-systems.com>,
Dmitry Kisil <d.kisil@inango-systems.com>
Subject: [hardknott] [PATCH 2/5] flex: correct license information
Date: Wed, 2 Jun 2021 14:27:17 +0100 [thread overview]
Message-ID: <20210602132720.2921099-2-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20210602132720.2921099-1-richard.purdie@linuxfoundation.org>
From: Nikolay Papenkov <n.papenkov@inango-systems.com>
License-Update: Corrected license information
flex package is under two licenses:
- "BSD-3-Clause" is provided in top-level COPYING file; the license
actually include third obligation (without the actual "3" numbering)
- "LGPL-2.0+" is explained by src/gettext.h
Signed-off-by: Dmitry Kisil <d.kisil@inango-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/recipes-devtools/flex/flex_2.6.4.bb | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/flex/flex_2.6.4.bb b/meta/recipes-devtools/flex/flex_2.6.4.bb
index 1d43d2228ac..54e7e01729d 100644
--- a/meta/recipes-devtools/flex/flex_2.6.4.bb
+++ b/meta/recipes-devtools/flex/flex_2.6.4.bb
@@ -3,12 +3,14 @@ DESCRIPTION = "Flex is a fast lexical analyser generator. Flex is a tool for ge
lexical patterns in text."
HOMEPAGE = "http://sourceforge.net/projects/flex/"
SECTION = "devel"
-LICENSE = "BSD-2-Clause"
+LICENSE = "BSD-3-Clause & LGPL-2.0+"
+LICENSE_${PN}-libfl = "BSD-3-Clause"
DEPENDS = "${@bb.utils.contains('PTEST_ENABLED', '1', 'bison-native flex-native', '', d)}"
BBCLASSEXTEND = "native nativesdk"
-LIC_FILES_CHKSUM = "file://COPYING;md5=e4742cf92e89040b39486a6219b68067"
+LIC_FILES_CHKSUM = "file://COPYING;md5=e4742cf92e89040b39486a6219b68067 \
+ file://src/gettext.h;beginline=1;endline=17;md5=9c05dda2f58d89b850c399cf22e1a00c"
SRC_URI = "https://github.com/westes/flex/releases/download/v${PV}/flex-${PV}.tar.gz \
file://run-ptest \
--
2.30.2
next prev parent reply other threads:[~2021-06-02 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 13:27 [hardknott] [PATCH 1/5] expat: set CVE_PRODUCT Richard Purdie
2021-06-02 13:27 ` Richard Purdie [this message]
2021-06-02 13:27 ` [hardknott] [PATCH 3/5] pkgconfig: update SRC_URI Richard Purdie
2021-06-02 13:27 ` [hardknott] [PATCH 4/5] package_rpm: pass XZ_THREADS to rpm Richard Purdie
2021-06-02 13:27 ` [hardknott] [PATCH 5/5] oeqa/runtime/rpm: Drop log message counting test component Richard Purdie
2021-06-02 14:34 ` [OE-core] [hardknott] [PATCH 1/5] expat: set CVE_PRODUCT Michael Opdenacker
2021-06-02 22:36 ` Richard Purdie
2021-06-03 16:19 ` Michael Opdenacker
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=20210602132720.2921099-2-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=d.kisil@inango-systems.com \
--cc=n.papenkov@inango-systems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.