[oe] [meta-qt5][WIP][PATCH] qt5: upgrade to latest revisions in 5.7 branch

[Martin Jansa]

On Wed, Jul 27, 2016 at 08:33:58PM +0300, Vesa Jääskeläinen wrote:
> 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.

It was done in first upgrade to 5.7 revisions, see:
https://github.com/meta-qt5/meta-qt5/commit/bf2cafa909a27250f853a823e9d7101307337e7a

> 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.

5.6 version is still maintained in krogoth branch, we had multiple qt5
versions in meta-qt5 before and it was causing more maintenance
overhead, I won't do it again

> 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"?

LICENSE and LIC_FILES_CHKSUM don't influence how the recipes are built
or which packages get installed in image. It's responsibility of the
integrator to disable e.g. PACKAGECONFIG options which include sources
with incompatible license - yes it could be improved - patches welcome.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20160727/48bf841b/attachment-0002.sig>