From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] qt5quickcontrols: update license file names
Date: Wed, 29 Aug 2018 22:50:01 +0200 [thread overview]
Message-ID: <20180829225001.576248e1@windsurf> (raw)
In-Reply-To: <20180829110517.15151-1-laurent.hartanerot@gmail.com>
Hello Laurent,
On Wed, 29 Aug 2018 13:05:17 +0200, Laurent Hartanerot wrote:
> From: Laurent Hartanerot <laurent.hartanerot@atos.net>
>
> Update license file name for qt5quickcontrols-5.6
>
> Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net>
I have applied your patch to the master branch, after doing two
additional tweaks, see below.
> +ifeq ($(BR2_PACKAGE_QT5_VERSION_LATEST),y)
> QT5QUICKCONTROLS_LICENSE = GPL-2.0 or GPL-3.0 or LGPL-3.0, GFDL-1.3 (docs)
> QT5QUICKCONTROLS_LICENSE_FILES = LICENSE.GPL2 LICENSE.GPL3 LICENSE.LGPL3 LICENSE.FDL
> +else
> +QT5QUICKCONTROLS_LICENSE = GPL-2.0 or GPL-3.0 or LGPL-3.0, GFDL-1.3 (docs)
The LICENSE variable was the same in both cases, so I moved it outside
of the version condition.
> +QT5QUICKCONTROLS_LICENSE_FILES = LICENSE.FDL LICENSE.GPLv2 LICENSE.GPLv3 LICENSE.LGPLv3
I moved LICENSE.FDL to the end of the list, so that the license files
are in the same order in both versions. It doesn't change anything
functionally speaking, but is a bit more consistent.
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-29 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 6:18 [Buildroot] [PATCH 1/1] qt5quickcontrols: update license file names Laurent Hartanerot
2018-08-29 8:23 ` Thomas Petazzoni
2018-08-29 11:05 ` [Buildroot] [PATCH v2 " Laurent Hartanerot
2018-08-29 20:50 ` 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=20180829225001.576248e1@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 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.