From: "Gaël PORTAY" <gael.portay@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 3/4] qt5virtualkeyboard: fix legal-info with 5.6
Date: Thu, 6 Sep 2018 03:43:59 -0400 [thread overview]
Message-ID: <20180906074358.puen25byqrukxoiq@archlinux> (raw)
In-Reply-To: <20180906093631.2fc13f1e@windsurf>
Thomas,
On Thu, Sep 06, 2018 at 09:36:31AM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 6 Sep 2018 03:32:21 -0400, Ga?l PORTAY wrote:
>
> > I found this [1]. I also asked to Qt and I am waiting for their
> > response.
> >
> > I guess this Qt5 module is available in Open license since 5.7;
>
> What do you call the "Open license" ?
>
I wanted to say that Qt VirtualKeyboard is available under GPLv3 since
5.7.
So I guess the version 2.0 is available only under the Qt Commercial
license.
> > thus 2.0 (5.6) is available only under their Commercial license.
>
> So the source code would be freely available, but can't be used without
> having their Commercial license ?
>
I do not know yet. I asked and I will tell you once I get a response
from them.
Ga?l
next prev parent reply other threads:[~2018-09-06 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 12:37 [Buildroot] [PATCH v1 0/4] qt5virtualkeyboard: fix build issues with 5.6 Gaël PORTAY
2018-09-03 12:37 ` [Buildroot] [PATCH v1 1/4] qt5virtualkeyboard: fix example build issue " Gaël PORTAY
2018-09-05 20:47 ` Thomas Petazzoni
2018-09-03 12:37 ` [Buildroot] [PATCH v1 2/4] qt5virtualkeyboard: fix target install " Gaël PORTAY
2018-09-05 20:51 ` Thomas Petazzoni
2018-09-06 8:12 ` Gaël PORTAY
2018-09-03 12:37 ` [Buildroot] [PATCH v1 3/4] qt5virtualkeyboard: fix legal-info " Gaël PORTAY
2018-09-05 21:11 ` Thomas Petazzoni
2018-09-06 7:32 ` Gaël PORTAY
2018-09-06 7:36 ` Thomas Petazzoni
2018-09-06 7:43 ` Gaël PORTAY [this message]
2018-09-03 12:37 ` [Buildroot] [PATCH v1 4/4] qt5virtualkeyboard: add hashes of 3rd-party licenses Gaël PORTAY
2018-09-05 21:34 ` Thomas Petazzoni
2018-09-09 10:42 ` Yann E. MORIN
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=20180906074358.puen25byqrukxoiq@archlinux \
--to=gael.portay@savoirfairelinux.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