From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,1/2] jasper: update license
Date: Tue, 9 Oct 2018 22:16:51 +0200 [thread overview]
Message-ID: <20181009201652.17189-1-fontaine.fabrice@gmail.com> (raw)
Add hash for license file and use SPDX short term identifier
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
Changes v1 -> v2 (after review of Thomas Petazzoni):
- Split patch in two: one for the license, the other one for bumping
the version
package/jasper/jasper.hash | 1 +
package/jasper/jasper.mk | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/jasper/jasper.hash b/package/jasper/jasper.hash
index b2b82178eb..8c4f2453ad 100644
--- a/package/jasper/jasper.hash
+++ b/package/jasper/jasper.hash
@@ -1,2 +1,3 @@
# Locally calculated
sha256 b50413b41bfc82ae419298b41eadcde1aa31f362fb9dc2ac089e5cbc19f60c24 jasper-version-2.0.13.tar.gz
+sha256 4ad1bb42aff888c4403d792e6e2c5f1716d6c279fea70b296333c9d577d30b81 LICENSE
diff --git a/package/jasper/jasper.mk b/package/jasper/jasper.mk
index 2aa3f9d554..9dc46b18d6 100644
--- a/package/jasper/jasper.mk
+++ b/package/jasper/jasper.mk
@@ -7,7 +7,7 @@
JASPER_VERSION = version-2.0.13
JASPER_SITE = $(call github,mdadams,jasper,$(JASPER_VERSION))
JASPER_INSTALL_STAGING = YES
-JASPER_LICENSE = JasPer License Version 2.0
+JASPER_LICENSE = JasPer-2.0
JASPER_LICENSE_FILES = LICENSE
JASPER_SUPPORTS_IN_SOURCE_BUILD = NO
JASPER_CONF_OPTS = \
--
2.17.1
next reply other threads:[~2018-10-09 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 20:16 Fabrice Fontaine [this message]
2018-10-09 20:16 ` [Buildroot] [PATCH v2,2/2] jasper: bump to version 2.0.14 Fabrice Fontaine
2018-10-10 19:18 ` [Buildroot] [PATCH v2,1/2] jasper: update license Thomas Petazzoni
2018-10-23 23:01 ` Peter Korsgaard
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=20181009201652.17189-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@busybox.net \
/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