From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] qt: define license
Date: Thu, 07 Feb 2013 23:40:41 +0100 [thread overview]
Message-ID: <51142D69.10008@lucaceresoli.net> (raw)
In-Reply-To: <5113DE02.3080308@mind.be>
Arnout Vandecappelle wrote:
>> How about the following?
>>
>> QT_LICENSE = LGPLv2.1 with exceptions or GPLv3
>> ifneq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
>> QT_LICENSE += or Digia Qt Commercial license
>> endif
>> QT_LICENSE_FILES = LICENSE.LGPL LGPL_EXCEPTION.txt LICENSE.GPL3
>
> Sounds good to me.
>
>
>> This way we still cannot automatically (and safely) set
>> _REDISTRIBUTE = NO, unless we add an explicit "Use commercial license"
>> knob in menuconfig.
>
> I don't think that's very important.
I agree. In fact I did not care about this in the v2 patch I just sent.
Luca
next prev parent reply other threads:[~2013-02-07 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:24 [Buildroot] [PATCH 1/5] ffmpeg: define license Luca Ceresoli
2013-02-06 16:24 ` [Buildroot] [PATCH 2/5] omap-u-boot-utils: " Luca Ceresoli
2013-02-06 16:24 ` [Buildroot] [PATCH 3/5] qt: " Luca Ceresoli
2013-02-06 16:58 ` Thomas Petazzoni
2013-02-06 20:04 ` Arnout Vandecappelle
2013-02-07 8:34 ` Luca Ceresoli
2013-02-07 17:01 ` Arnout Vandecappelle
2013-02-07 22:40 ` Luca Ceresoli [this message]
2013-02-06 16:24 ` [Buildroot] [PATCH 4/5] fbset: " Luca Ceresoli
2013-02-07 20:36 ` Peter Korsgaard
2013-02-06 16:24 ` [Buildroot] [PATCH 5/5] ccache: " Luca Ceresoli
2013-02-06 20:04 ` [Buildroot] [PATCH 1/5] ffmpeg: " Arnout Vandecappelle
2013-02-06 22:13 ` Peter Korsgaard
2013-02-07 8:38 ` Luca Ceresoli
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=51142D69.10008@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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.