From: Tom Rini <trini@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
"Cooper Jr., Franklin" <fcooper@ti.com>
Subject: Re: [PATCH 3/4] board-port-labs: Use new SRCIPK_PRESERVE_GIT git feature in sourceipk.bbclass
Date: Fri, 23 Aug 2013 11:16:19 -0400 [thread overview]
Message-ID: <52177CC3.4010804@ti.com> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED101596DCDC5@DLEE11.ent.ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/23/2013 10:36 AM, Maupin, Chase wrote:
>> -----Original Message----- From:
>> meta-arago-bounces@arago-project.org [mailto:meta-arago-
>> bounces@arago-project.org] On Behalf Of Cooper Jr., Franklin
>> Sent: Thursday, August 22, 2013 5:11 PM To:
>> meta-arago@arago-project.org Cc: Cooper Jr., Franklin Subject:
>> [meta-arago] [PATCH 3/4] board-port-labs: Use new
>> SRCIPK_PRESERVE_GIT git feature in sourceipk.bbclass
[snip]
>> +++ b/meta-arago-distro/recipes-tisdk/board-port-labs/board-port-
>> labs-u-boot_git.bb @@ -0,0 +1,36 @@ +DESCRIPTION = "Git
>> repositories containing sample board port code" +HOMEPAGE =
>> "https://gitorious.org/sitara-board-port" +LICENSE = "GPLv2"
>
> U-Boot license in the base recipes are GPLv2+ so this probably
> needs to match.
>
>> + +LIC_FILES_CHKSUM =
>> "file://../LICENSE;md5=d9fb2a547cd8e6bb75c0ecf427a139a9"
>
> Why not use the file in the sources at Licenses/gpl-2.0.txt?
>
> Tom, with all the licenses in that directory would you stay u-boot
> is still GPLv2+? It seems those other licenses are for the stand
> alone apps, but for source distribution should this license be
> updated to include the other licenses?
So, with the change in how we've noted licensing, from boiler plates
in every file and a top-level LICENSE file to having SPDX tags in
every file, we haven't changed the terms (modulo a few cases of
correcting GPLv2+ files to GPLv2) of the project. We have however
made it clearer where future problems may lie. We are still GPLv2+,
however all of the kernel code we have that is GPLv2 would make a
future license change harder.
In sum, yes, we're GPLv2+ and Licenses/gpl-2.0.txt is fine to point at
since it says "or later" in it.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSF3zDAAoJENk4IS6UOR1WlbgP/A8j97ylSD93oF/g31CqN9JA
PrtU80fJTpsSiCRt8JyGCAekfeP8/ZeoCnWfrpa4F6ARTPv2q2kgJQ9cqmBKYrIm
HNUOEGC6iMSaEmAP0LDbc9KPGkevvI5eyzSvUwbIMX2OiL87hHnuhCfAnAqPfyDK
sCGDju1PK72R7E1FsZjVdxJylx/Z81FWGas6+KlOL4Cj9QLvVqkKBrzloFquJGDe
g1nqZgv20qOQiWnR8l2CY8H6g7tEUBf6v1oSfOkyU7fKJcl8AL3wAAG00/kqhXfj
/kUmwo+uAGVSd2X0z6vKKgRXDI2iOzzycJ93CfgiTA2enCTkyjRMCQU/mrp47pdD
UD8r97GRipPboxoFGJAbfZOKVV24CWB0mU5aL9bfvDiFyhit6RatZYUajO7edgTK
QNjh2PIRMN2Jx1MXD4qhg47buOU4jY4Drmk5NLo/f4ykippW6Kw5jC4ZUuaQbCqe
aFp1oj/NK6v8swN7SYy+Nq362Xazsit1BJR0g86/Wdn6g91AyEfOIdNQvOpbGrON
1T6MbCFK7Pu3YjsfvgOVfFO2JTEnGsdJzHPPci8FAfDfnJO8+wobH9Gu6AqASTjO
wuVVbaGGQYTDQx2AndNa8usej7WhlPkoyMI0n4OD5EcT2Tz55eGhCzN7VfMo3ByB
vbMoTUYcyPuO53GivSPU
=icLI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-08-23 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 22:10 [PATCH 1/4] gst-plugins-bad: Remove with-plugins from configuration Franklin S. Cooper Jr
2013-08-22 22:10 ` [PATCH 2/4] sourceipk: Add ability to preserve Git repository Franklin S. Cooper Jr
2013-08-23 14:25 ` Maupin, Chase
2013-08-22 22:10 ` [PATCH 3/4] board-port-labs: Use new SRCIPK_PRESERVE_GIT git feature in sourceipk.bbclass Franklin S. Cooper Jr
2013-08-23 14:36 ` Maupin, Chase
2013-08-23 15:04 ` Cooper Jr., Franklin
2013-08-23 15:25 ` Maupin, Chase
2013-08-23 15:16 ` Tom Rini [this message]
2013-08-22 22:10 ` [PATCH 4/4] packagegroup-arago-tisdk-amsdk-sdk-host: Use new board-port-labs recipe Franklin S. Cooper Jr
2013-08-23 14:39 ` Maupin, Chase
2013-08-23 20:31 ` [PATCH 1/4] gst-plugins-bad: Remove with-plugins from configuration Denys Dmytriyenko
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=52177CC3.4010804@ti.com \
--to=trini@ti.com \
--cc=chase.maupin@ti.com \
--cc=fcooper@ti.com \
--cc=meta-arago@arago-project.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.