From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster <akuster@mvista.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] nettle: update to version 3.0
Date: Tue, 15 Jul 2014 16:09:05 +0100 [thread overview]
Message-ID: <1405436945.20402.9.camel@ted> (raw)
In-Reply-To: <53C53683.7050107@mvista.com>
On Tue, 2014-07-15 at 07:11 -0700, akuster wrote:
> On 07/15/2014 06:49 AM, Burton, Ross wrote:
> > On 15 July 2014 14:27, Armin Kuster <akuster@mvista.com> wrote:
> >> Add GNUv3 license
> > If nettle 3 contains GPLv3 code then we probably don't want to remove
> > nettle 2.1, for people building without any v3 code in the images.
>
> They have what they call dual license in 3.x ( GPLv2 or GPLv3). We
> certainly can keep 2.7.1
Is it "GPLv2 or GPLv3" or "GPLv2 and GPLv3". There is a big difference
and the LICENSE field needs to be set correctly (&& or || in the license
field).
Cheers,
Richard
next prev parent reply other threads:[~2014-07-15 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:27 [meta-oe][PATCH] nettle: update to version 3.0 Armin Kuster
2014-07-15 13:49 ` Burton, Ross
2014-07-15 14:11 ` akuster
2014-07-15 15:09 ` Richard Purdie [this message]
2014-07-15 15:19 ` akuster
2014-07-15 14:19 ` akuster808
2014-07-15 15:13 ` Saul Wold
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=1405436945.20402.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster@mvista.com \
--cc=openembedded-core@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