All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH] licenses: rename NOKIA-TPLA-2.4 to DIGIA-TPLA-2.4
Date: Sat, 15 Mar 2014 16:27:44 +0100	[thread overview]
Message-ID: <20140315152744.GL3759@jama> (raw)
In-Reply-To: <2D16971D-4F6B-4162-8CD6-E28C34160B11@gmail.com>

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

On Sat, Mar 15, 2014 at 08:22:33AM -0700, Khem Raj wrote:
> 
> On Mar 15, 2014, at 8:20 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > On Sat, Mar 15, 2014 at 08:04:14AM -0700, Khem Raj wrote:
> >> 
> >> On Mar 15, 2014, at 7:54 AM, Jonathan Liu <net147@gmail.com> wrote:
> >> 
> >>> The license agreement doesn't mention Nokia anymore after Qt was
> >>> acquired by Digia.
> >>> 
> >>> Signed-off-by: Jonathan Liu <net147@gmail.com>
> >>> ---
> >>> licenses/{NOKIA-TPLA-2.4 => DIGIA-TPLA-2.4} | 0
> >>> recipes-qt/qt5/qt3d.inc                     | 2 +-
> >>> 2 files changed, 1 insertion(+), 1 deletion(-)
> >>> rename licenses/{NOKIA-TPLA-2.4 => DIGIA-TPLA-2.4} (100%)
> >>> 
> >>> diff --git a/licenses/NOKIA-TPLA-2.4 b/licenses/DIGIA-TPLA-2.4
> >>> similarity index 100%
> >>> rename from licenses/NOKIA-TPLA-2.4
> >>> rename to licenses/DIGIA-TPLA-2.4
> >>> diff --git a/recipes-qt/qt5/qt3d.inc b/recipes-qt/qt5/qt3d.inc
> >>> index 78b9ecc..74c4cad 100644
> >>> --- a/recipes-qt/qt5/qt3d.inc
> >>> +++ b/recipes-qt/qt5/qt3d.inc
> >>> @@ -2,7 +2,7 @@ require qt5.inc
> >>> 
> >>> DEPENDS += "qtdeclarative"
> >>> 
> >>> -LICENSE = "GFDL-1.3 & LGPL-2.1 & NOKIA-TPLA-2.4 | GPL-3.0"
> >>> +LICENSE = "GFDL-1.3 & LGPL-2.1 & DIGIA-TPLA-2.4 | GPL-3.0”
> >> 
> >> you need to rename the license file too
> > 
> > he did :)
> > 
> > sorry it's my mistake, when I was updating license text from newer qt3d
> > repo I haven't noticed nokia->digia change between whitespace changes
> > 
> > should we use the same text for dylan,dora,master even when older qt3d
> > revisions have older text? I think it would be better to have
> > DIGIA-TPLA-2.4 everywhere.
> 
> 
> I think call it QT-TPLA-2.4 and then the name becomes universal

name yes, but still the text would be different in qt3d repo and our
text before this qt3d commit which changed it to digia:
https://qt.gitorious.org/qt/qt3d/commit/06eb6c1060743b7dbd61bfa9a169f2a1cd44af39#LICENSE.PREVIEW.COMMERCIAL

alternatively we can keep both texts (remove my update of license text
from NOKIA-TPLA-2.4 and keep separate DIGIA-TPLA-2.4 and use the right
one based on SRCREV used in recipe.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

  reply	other threads:[~2014-03-15 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 14:54 [meta-qt5][PATCH] licenses: rename NOKIA-TPLA-2.4 to DIGIA-TPLA-2.4 Jonathan Liu
2014-03-15 15:04 ` Khem Raj
2014-03-15 15:20   ` Martin Jansa
2014-03-15 15:22     ` Khem Raj
2014-03-15 15:27       ` Martin Jansa [this message]
2014-03-15 15:55         ` Khem Raj
2014-03-15 18:03           ` 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=20140315152744.GL3759@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 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.