From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/exiv2: cleanup options and licenses
Date: Sun, 26 May 2019 22:36:38 +0200 [thread overview]
Message-ID: <20190526223638.43122149@windsurf> (raw)
In-Reply-To: <20190508103129.100751-1-nicolas.serafini@sensefly.com>
Hello Nicolas,
Thanks for the patch!
On Wed, 8 May 2019 10:32:21 +0000
Nicolas Serafini <nicolas.serafini@sensefly.com> wrote:
> exiv2 no longer requires a commercial option for lens database
> integration since version 0.27.
>
> Legacy handling for the removed options _COMMERCIAL and _LENSDATA is
> not needed, since now they are always enabled.
While I understand the reasoning for the removal of the _COMMERCIAL
option, I don't understand the relationship with the removal of the
_LENSDATA option. Why is this option removed and the installation of
lens data made mandatory ?
And if there's a reason for it, why is it done as part of the patch
dropping the _COMMERCIAL option ?
> diff --git a/package/exiv2/exiv2.hash b/package/exiv2/exiv2.hash
> index f99cb8cb87..b753c03854 100644
> --- a/package/exiv2/exiv2.hash
> +++ b/package/exiv2/exiv2.hash
> @@ -1,3 +1,4 @@
> # Locally calculated
> sha256 1b3766b2c203ce213a4195de14d61694017ec1a69d15d4575bccecef130990fe exiv2-0.27.1.tar.gz
> sha256 a7ba75cb966aca374711e2af49e5f3aea6a4443a803440f5d93e73a5a1222f66 COPYING
> +sha256 46cde7dc11e64c78d650b4851b88f6704b4665ff60f22a1caf68ceb15e217e5b COPYING-CMAKE-SCRIPTS
> diff --git a/package/exiv2/exiv2.mk b/package/exiv2/exiv2.mk
> index ba9d9b7303..c557c08fb8 100644
> --- a/package/exiv2/exiv2.mk
> +++ b/package/exiv2/exiv2.mk
> @@ -7,27 +7,16 @@
> EXIV2_VERSION = 0.27.1
> EXIV2_SITE = $(call github,Exiv2,exiv2,$(EXIV2_VERSION))
> EXIV2_INSTALL_STAGING = YES
> +EXIV2_LICENSE = GPL-2.0+ BSD-3-Clause
The proper separator for the _LICENSE variable is a comma, i.e:
EXIV2_LICENSE = GPL-2.0+, BSD-3-Clause
I can fix that when applying, but I'd like to understand the rationale
for the removal of the _LENSDATA option.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-26 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 10:32 [Buildroot] [PATCH v2] package/exiv2: cleanup options and licenses Nicolas Serafini
2019-05-26 20:36 ` Thomas Petazzoni [this message]
2019-05-26 21:50 ` Arnout Vandecappelle
2019-05-27 7:06 ` Thomas Petazzoni
2019-06-03 8:49 ` Nicolas Serafini
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=20190526223638.43122149@windsurf \
--to=thomas.petazzoni@bootlin.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