bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gplv3 files and updates


From: Yoann Vandoorselaere
Subject: Re: gplv3 files and updates
Date: Wed, 04 Jul 2007 09:00:40 +0200

Le mercredi 04 juillet 2007 à 03:12 +0200, Simon Josefsson a écrit :
> Paul Eggert <address@hidden> writes:
> 
> > Bruno Haible <address@hidden> writes:
> >
> >> The sequence of events that I'm hoping for is this:
> >>   - First, get agreement that all projects that use gnulib are OK with 
> >> GPLv3.
> >
> > I don't hear any objection, so let's assume there's agreement on that topic.
> 
> I'd prefer to wait a bit, to get a feeling of how serious the GPLv2-only
> situation is.  We can implement a --gplv3 parameter om gnulib if you
> don't want to have GPLv2 mentioned in your sources.
> 
> GnuTLS links to a GPLv2-only project (liblzo) and until that issue has
> been settled, it would cause problems if gnulib became GPLv3-only.

Some people are not decided to switch to GPLv3 yet. Some are even
suppressing the "or later" clause of the GPLv2 license until they know
what they are going to do in the future. 

An example of this is Snort, which changed the upcoming Snort 2.7
license from GPLv2 or later to GPLv2 only. Check
http://www.snort.org/about_snort/licenses/gplv2.html for the background.

Snort can use libprelude, which is GPLv2 or later.
Libprelude use both GnuTLS and Gnulib.

You can see the problem if GnuLib were to force (L)GPLv3 only.

-- 
Yoann Vandoorselaere | Responsable R&D / CTO | PreludeIDS Technologies
Tel: +33 (0)8 70 70 21 58                  Fax: +33(0)4 78 42 21 58
http://www.prelude-ids.com





reply via email to

[Prev in Thread] Current Thread [Next in Thread]