www/licenses gpl-faq.html

[Brett Smith]

CVSROOT:        /web/www
Module name:    www
Changes by:     Brett Smith <brett>     09/05/05 16:27:47

Modified files:
        licenses       : gpl-faq.html 

Log message:
        link to #GPLIncompatibleLibs from #NonFreeTools

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.html?cvsroot=www&r1=1.141&r2=1.142

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -b -r1.141 -r1.142
--- gpl-faq.html        14 Nov 2008 16:24:07 -0000      1.141
+++ gpl-faq.html        5 May 2009 16:27:05 -0000       1.142
@@ -2279,12 +2279,14 @@
 study it, or record it, usually makes no difference for issues
 concerning the licensing of that source code.</p>
 
-<p>However, if you link non-free libraries with the source code, that would be
-an issue you need to deal with.  It does not preclude releasing the source
-code under the GPL, but if the libraries don't fit under the &ldquo;system
-library&rdquo; exception, you should affix an explicit notice giving
-permission to link your program with them.  The FSF can give you advice on
-doing this.</p>
+<p>However, if you link non-free libraries with the source code, that
+would be an issue you need to deal with.  It does not preclude
+releasing the source code under the GPL, but if the libraries don't
+fit under the &ldquo;system library&rdquo; exception, you should affix
+an explicit notice giving permission to link your program with
+them.  <a href="#GPLIncompatibleLibs">Our FAQ about using
+GPL-incompatible libraries</a> provides more information about
+how to do that.</p>
 </dd>
 
 
@@ -3344,7 +3346,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2008/11/14 16:24:07 $
+$Date: 2009/05/05 16:27:05 $
 <!-- timestamp end -->
 </p>
 </div>