Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] nettle: update package to 3.1.1 version.
Date: Wed, 08 Jul 2015 00:04:36 +0100	[thread overview]
Message-ID: <1436310276.27597.198.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=Vb889E6fcJJyN93MRwUfbShLrSa1S-79sQyoSHChYnYg@mail.gmail.com>

On Tue, 2015-07-07 at 14:03 -0700, Andre McCurdy wrote:
> On Tue, Jul 7, 2015 at 1:30 PM, Burton, Ross <ross.burton@intel.com> wrote:
> > On 7 July 2015 at 21:09, akuster808 <akuster808@gmail.com> wrote:
> >>
> >> which recipe? 2.7.1 / 3.1 or both?
> >>
> >> - armin
> >> ( sucks at this licensing stuff)
> >
> >
> > So: 2.7.1 is "LGPL" (v2).
> >
> > 3.1.1 is GPLv2+ or LGPLv3+.
> >
> > An "interesting" choice to say the least. Because the v2 bit is not L, I'm
> > wondering if we will need to keep both versions.  But a 3.1.1 recipe with
> > GPLv2+ *or* LGPLv3+ would be a good start.
> 
> I'd vote YES to keeping the LGPLv2 version available.
> 
> GPL libraries are normally off limits for closed source apps, so the
> new licensing options would be a problem for anyone with a proprietary
> application using nettle in a distro which can't use [L]GPLv3. (I'm in
> that category...).

Surely if you can't use [L]GPLv3, you want the 3.1.1 version which is
GPLv2 (or other things)?

Cheers,

Richard





  reply	other threads:[~2015-07-07 23:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 13:18 [PATCH 0/2] gnutls update to 3.4.1 Armin Kuster
2015-06-28 13:18 ` [PATCH 1/2] nettle: update package to 3.1.1 version Armin Kuster
2015-07-01 22:42   ` Burton, Ross
2015-07-02 11:30     ` Anders Darander
2015-07-02 12:00       ` Burton, Ross
2015-07-02 17:04     ` akuster808
2015-07-02 18:46       ` Burton, Ross
2015-07-02 22:02         ` akuster808
2015-07-03  7:07       ` Anders Darander
2015-07-03  8:41         ` Paul Eggleton
2015-07-03 21:54         ` akuster808
2015-07-04 11:38           ` Paul Eggleton
2015-07-06 13:04             ` Burton, Ross
2015-07-06 13:58               ` Paul Eggleton
2015-07-07  5:46                 ` Anders Darander
2015-07-07  5:34       ` Anders Darander
2015-07-07 10:40         ` Burton, Ross
2015-07-07 20:09           ` akuster808
2015-07-07 20:30             ` Burton, Ross
2015-07-07 21:03               ` Andre McCurdy
2015-07-07 23:04                 ` Richard Purdie [this message]
2015-07-07 23:56                   ` Andre McCurdy
2015-07-08 13:03                     ` Anders Darander
2015-06-28 13:18 ` [PATCH 2/2] gnutls: update to 3.4.1 Armin Kuster
  -- strict thread matches above, loose matches on Subject: below --
2015-06-01 14:12 [PATCH 0/2] Gnutls 3.4.1 update Armin Kuster
2015-06-01 14:13 ` [PATCH 1/2] nettle: update package to 3.1.1 version Armin Kuster

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=1436310276.27597.198.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.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