From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] libunistring: Update version 0.9.6 -> 0.9.7
Date: Mon, 12 Dec 2016 17:16:22 +0200 [thread overview]
Message-ID: <1481555783-3130-1-git-send-email-maxin.john@intel.com> (raw)
The license has changed from LGPLv3+ to "LGPLv3+ or GPLv2"
* README (Copyright): Rewrite section
* doc/libunistring.texi (Licenses): Change accordingly
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
.../{libunistring_0.9.6.bb => libunistring_0.9.7.bb} | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
rename meta/recipes-support/libunistring/{libunistring_0.9.6.bb => libunistring_0.9.7.bb} (70%)
diff --git a/meta/recipes-support/libunistring/libunistring_0.9.6.bb b/meta/recipes-support/libunistring/libunistring_0.9.7.bb
similarity index 70%
rename from meta/recipes-support/libunistring/libunistring_0.9.6.bb
rename to meta/recipes-support/libunistring/libunistring_0.9.7.bb
index bb70122..f77a210 100644
--- a/meta/recipes-support/libunistring/libunistring_0.9.6.bb
+++ b/meta/recipes-support/libunistring/libunistring_0.9.7.bb
@@ -13,16 +13,18 @@ DESCRIPTION = "Text files are nowadays usually encoded in Unicode, and may\
HOMEPAGE = "http://www.gnu.org/software/libunistring/"
SECTION = "devel"
-LICENSE = "GPLv3 & LGPLv3"
-LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
- file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6"
+LICENSE = "LGPLv3+ | GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6 \
+ file://README;beginline=45;endline=65;md5=08287d16ba8d839faed8d2dc14d7d6a5 \
+ file://doc/libunistring.texi;md5=b86c9fd7acaac623017239640631912c \
+ "
SRC_URI = "${GNU_MIRROR}/libunistring/libunistring-${PV}.tar.gz \
file://iconv-m4-remove-the-test-to-convert-euc-jp.patch \
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
"
-SRC_URI[md5sum] = "dfae4ff5583649ed24d8f368f1d0543b"
-SRC_URI[sha256sum] = "9625eec2507f4789ebb6fc48ebda98be0e0168979a2f68aa8b680bf8eeabbd47"
+SRC_URI[md5sum] = "8e663454aa372181ee8e46edaa3ba4c8"
+SRC_URI[sha256sum] = "9ce081cbee1951b55597b30e7030bda9d7b2f034ef901a135ff3a020be5a41e5"
inherit autotools texinfo
BBCLASSEXTEND = "native nativesdk"
--
2.4.0
next reply other threads:[~2016-12-12 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 15:16 Maxin B. John [this message]
2016-12-12 15:16 ` [PATCH 2/2] harfbuzz: upgrade to 1.3.4 Maxin B. John
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=1481555783-3130-1-git-send-email-maxin.john@intel.com \
--to=maxin.john@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