On Thu, Jul 16, 2015 at 03:38:50PM +0200, [email protected] wrote:
> 
> > Re: [ptxdist] [PATCH] nettle: fix license information tag
> >
> > On Fri, Jul 10, 2015 at 02:11:33PM +0200, Oliver Graute wrote:
> > > Since June 2009 (version 2.0) Nettle is a GNU Package
> > >
> > > Signed-off-by: Oliver Graute <[email protected]>
> > > ---
> > >  rules/nettle.make |    2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/rules/nettle.make b/rules/nettle.make
> > > index 7ce57a4..e59c88e 100644
> > > --- a/rules/nettle.make
> > > +++ b/rules/nettle.make
> > > @@ -23,7 +23,7 @@ NETTLE_SUFFIX   := tar.gz
> > >  NETTLE_URL   := http://www.lysator.liu.se/~nisse/archive/$
> > (NETTLE).$(NETTLE_SUFFIX)
> > >  NETTLE_SOURCE   := $(SRCDIR)/$(NETTLE).$(NETTLE_SUFFIX)
> > >  NETTLE_DIR   := $(BUILDDIR)/$(NETTLE)
> > > -NETTLE_LICENSE   := unknown
> > > +NETTLE_LICENSE   := LGPLv3,GPLv2,GPLv3
> >
> > Hmmm, I didn't check everything, but I'm seeing LGPLv2.1+ and not much
> > else.
> 
> I found this on the project page of nettle:
> 
> "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. A few of the individual files are licensed under more
> permissive terms, or in the public domain. To find the current status of
> particular files, you have to read the copyright notices at the top of the
> files."
> 
> http://www.lysator.liu.se/~nisse/nettle/nettle.html#Copyright
> https://en.wikipedia.org/wiki/Nettle_(cryptographic_library)

That's for version 3.x I think. We still have 2.7.1.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
[email protected]

Reply via email to