[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/11/10 20:04:03

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Rephrased the part of GPL exceptions a little bit

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.69&tr2=1.70&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.69 
administration/docs/hacking_savannah/hacking_savannah.texi:1.70
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.69     Wed Nov 
10 19:41:24 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Wed Nov 10 
20:04:01 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.69 2004/11/10 19:41:24 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.70 2004/11/10 20:04:01 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -2579,13 +2579,22 @@
 Those URLs are required readings for any serious Savannah hacker. Some
 of us even think they should be taught in Computer Science lessons :)
 
-Keep in mind that a project released under the GNU GPL, be it hosted
-at Savannah or not, cannot be legally linked to software released
-under a GPL-incompatible license, unless both the project and the
-dependency make special exceptions to their licenses. We feel it is a
-delicate point and urge you to contact the GPL Compliance Lab in such
-case. Just remember that dependencies of a program released under the
-GNU GPL has to be compatible with this license.
+
+Keep in mind that a project released under the GNU GPL cannot have
+GPL-incompatible dependencies. This independent from the Savannah
+hosting criteria.
+
+This is something we check during the approval nonetheless, because we
+require projects to have a clean licensing.
+
+Actually there is a way to link a GPL program with a GPL-incompatible
+library, check
address@hidden://www.gnu.org/@/licenses/@/gpl-faq.html#GPLIncompatibleLibs}. We
+feel it is a delicate point and urge you to contact the GPL Compliance
+Lab in such case. In addition, this solution is not recommended, as
+the project will be incompatible with the GNU GPL (the exception is
+not part of the standard GNU GPL). Anyone can remove this
+``exception'' though.
 
 The GNU Lesser General Public License (LGPL) is basically compatible
 with any dependencies linked dynamicaly (to keep it short). In fact,