Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <dachaac@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][WIP][PATCH] qt5: upgrade to latest revisions in 5.7 branch
Date: Wed, 27 Jul 2016 20:33:58 +0300	[thread overview]
Message-ID: <3f91bfa8-d87d-9e79-c38d-e4b10a74c1ae@gmail.com> (raw)
In-Reply-To: <20160727154953.13918-1-Martin.Jansa@gmail.com>

Hi,

...snip...

I did not see the license change from GPLv2/LGPLv2.1 -> GPLv3/LGPLv3. 
Was this some previous change or just forgotten one? With quick look I 
did not spot GPLv3 mentions in meta-qt5 in github.

Because of this dramatic license change I would recommend keeping old 
5.6 available so if one blacklists GPLv3 & LGPLv3 then old one gets 
picked up.

I suppose right way to handle this special licensing case is to define 
license as being by default GPLv3 | LGPLv3 and then if company purchases 
license for Qt5.7 then override recipes license with something like 
LICENSE_pn_qt5 = "commercial" in local.conf or own layer with matching 
.bbappend?

Another related question is that what is recommended method to select 
license? As some software is under multiple licenses and then we would 
select one of those licenses and then only want that license to be 
collected for image.

I suppose this would need similar method as what PACKAGECONFIG[...] but 
with LIC_FILES_CHKSUM[foo] and then you select one with LICENSE="foo"?

Thanks,
Vesa Jääskeläinen


  reply	other threads:[~2016-07-27 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 15:49 [meta-qt5][WIP][PATCH] qt5: upgrade to latest revisions in 5.7 branch Martin Jansa
2016-07-27 17:33 ` Vesa Jääskeläinen [this message]
2016-07-27 17:52   ` Martin Jansa
2016-08-04  9:38 ` [meta-qt5][PATCH] " Martin Jansa
2016-08-04 13:04 ` [meta-qt5][PATCH] qt5-opengles2-test: remove Martin Jansa

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=3f91bfa8-d87d-9e79-c38d-e4b10a74c1ae@gmail.com \
    --to=dachaac@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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