From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] qt/qt5script: Remove the GPLv2 licence file
Date: Wed, 22 Jul 2015 11:03:08 +0200 [thread overview]
Message-ID: <20150722110308.105925d7@free-electrons.com> (raw)
In-Reply-To: <1437554012-25241-1-git-send-email-corjon.j@ecagroup.com>
Dear Julien Corjon,
On Wed, 22 Jul 2015 10:33:31 +0200, Julien Corjon wrote:
> Signed-off-by: Julien Corjon <corjon.j@ecagroup.com>
> ---
> package/qt5/qt5script/qt5script.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/qt5/qt5script/qt5script.mk b/package/qt5/qt5script/qt5script.mk
> index 7f0efbb..c654fe5 100644
> --- a/package/qt5/qt5script/qt5script.mk
> +++ b/package/qt5/qt5script/qt5script.mk
> @@ -12,7 +12,7 @@ QT5SCRIPT_INSTALL_STAGING = YES
>
> ifeq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
> QT5SCRIPT_LICENSE = LGPLv2.1 with exception or LGPLv3 or GPLv2
Is the "or GPLv2" still valid, despite the GPLv2 file not being there?
> -QT5SCRIPT_LICENSE_FILES = LICENSE.LGPLv21 LGPL_EXCEPTION.txt LICENSE.LGPLv3 LICENSE.GPLv2
> +QT5SCRIPT_LICENSE_FILES = LICENSE.LGPLv21 LGPL_EXCEPTION.txt LICENSE.LGPLv3
> else
> QT5SCRIPT_LICENSE = Commercial license
> QT5SCRIPT_REDISTRIBUTE = NO
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-22 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 8:33 [Buildroot] [PATCH 1/2] qt/qt5script: Remove the GPLv2 licence file Julien Corjon
2015-07-22 8:33 ` [Buildroot] [PATCH 2/2] qt/qt5base: Fix big endian image conversion Julien Corjon
2015-07-22 9:04 ` Thomas Petazzoni
2015-07-22 9:03 ` Thomas Petazzoni [this message]
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=20150722110308.105925d7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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