Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][WIP-for-5.7][meta-qt5] qtwebengine: update LICENSE/LIC_FILES_CHKSUM
Date: Fri, 19 Feb 2016 18:53:45 +0100	[thread overview]
Message-ID: <20160219175345.GA2588@jama> (raw)
In-Reply-To: <1455890654-2396-1-git-send-email-Martin.Jansa@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Fri, Feb 19, 2016 at 03:04:14PM +0100, Martin Jansa wrote:
> * this should be part of the upgrade to 5.7, but the changes
>   are important and separate change has higher chance to be
>   noticed
> * it's highly recommended to read:
>   http://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
>   to find out how you're affected check which files/tools are
>   included in your builds
>   OE @ ~/projects/qt-project/qtwebengine $ git grep QT_BEGIN_LICENSE | sed 's/^[^:]*://g' | sort | uniq -c
>      11 ## $QT_BEGIN_LICENSE:GPL-EXCEPT$
>      67 ** $QT_BEGIN_LICENSE:BSD$
>      17 ** $QT_BEGIN_LICENSE:FDL$
>      61 ** $QT_BEGIN_LICENSE:GPL-EXCEPT$
>     261 ** $QT_BEGIN_LICENSE:LGPL$
> * change in chromium's LICENSE is only copyright year update

With few more smaller fixes this finally builds (including nativesdk).

Latest version of all these patches are in jansa/master-5.7.

Fixes for currently used 5.6 version are already in master-next (and
jansa/master).

Regards,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2016-02-19 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 14:04 [PATCH][WIP-for-5.7][meta-qt5] qtwebengine: update LICENSE/LIC_FILES_CHKSUM Martin Jansa
2016-02-19 17:53 ` Martin Jansa [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=20160219175345.GA2588@jama \
    --to=martin.jansa@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