Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: akuster <akuster@mvista.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] [v2] nettle: update to version 3.0
Date: Wed, 16 Jul 2014 10:18:23 -0700	[thread overview]
Message-ID: <53C6B3DF.3040300@linux.intel.com> (raw)
In-Reply-To: <53C54A18.4030907@mvista.com>

On 07/15/2014 08:34 AM, akuster wrote:
>
> On 07/15/2014 08:24 AM, Burton, Ross wrote:
>> On 15 July 2014 16:13, Armin Kuster <akuster@mvista.com> wrote:
>>> +LICENSE = "LGPLv2.1 & GPLv2 & GPLv3"
>> The manual says:
>>
>> "Nettle is dual licenced under the GNU General Public License version
>> 2 or later, and the GNU Lesser General Public License version 3 or
>> later. When using Nettle, you must comply fully with all conditions of
>> at least one of these licenses."
>>
>> So I think you mean LICENSE="GPLv2+ | LGPLv3+"
>>
>> I'm undecided whether this means we can drop the old Nettle or not...
>
> Ok. I will wait for the dust to settle before I submit patch v3.
>

So I checked on this and it would be an or ('|').

The only other concern I have is there is a COPYING.GPLv3, you might 
want to check with the upstream what the intent of having that License 
file is for, do they intend on some parts being v3 and if so which parts?

I am not sure if the INCOMPATIBLE_LICENSE will handle the OR properly, 
but we should just have one version.

Sau!

> - Armin
>>
>> Ross
>


  reply	other threads:[~2014-07-16 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 15:13 [meta-oe][PATCH] [v2] nettle: update to version 3.0 Armin Kuster
2014-07-15 15:21 ` Saul Wold
2014-07-15 15:35   ` akuster
2014-07-15 15:24 ` Burton, Ross
2014-07-15 15:34   ` akuster
2014-07-16 17:18     ` Saul Wold [this message]
2014-07-16 21:23       ` Burton, Ross

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=53C6B3DF.3040300@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=akuster@mvista.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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