[Top][All Lists]

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

www/licenses lgpl-java.html

From: Brett Smith
Subject: www/licenses lgpl-java.html
Date: Fri, 23 Sep 2011 15:44:20 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Brett Smith <brett>     11/09/23 15:44:20

Modified files:
        licenses       : lgpl-java.html 

Log message:
        adjust derivative works wording, per 709536


Index: lgpl-java.html
RCS file: /web/www/www/licenses/lgpl-java.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- lgpl-java.html      20 Sep 2011 08:14:57 -0000      1.16
+++ lgpl-java.html      23 Sep 2011 15:43:39 -0000      1.17
@@ -21,11 +21,12 @@
 It has always been the FSF's position that dynamically linking
 applications to libraries creates a single work derived from both the
 library code and the application code.  The GPL requires that all
-derivative works be licensed under the GPL, an effect which can be
-described as &ldquo;hereditary.&rdquo;  So, if an application links to a 
-licensed under the GPL, the application too must be licensed under the
-GPL.  By contrast, libraries licensed under the GNU Lesser General
-Public License (LGPL) may be linked to proprietary applications. </p> 
+derivative works be licensed as a whole under the terms of the GPL, an
+effect which can be described as &ldquo;hereditary.&rdquo; So, if an
+application links to a library licensed under the GPL, the application
+too must be licensed under the GPL.  By contrast, libraries licensed
+under the GNU Lesser General Public License (LGPL) may be linked to
+proprietary applications. </p>
 In July of 2003, Slashdot published a story claiming that I had claimed
@@ -106,7 +107,7 @@
 <!-- timestamp start -->
-$Date: 2011/09/20 08:14:57 $
+$Date: 2011/09/23 15:43:39 $
 <!-- timestamp end -->

reply via email to

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