www/licenses gpl-howto.html

[Brett Smith]

CVSROOT:        /web/www
Module name:    www
Changes by:     Brett Smith <brett>     07/07/12 15:57:10

Modified files:
        licenses       : gpl-howto.html 

Log message:
        More updates for the version 3 releases.  The main focus here is making 
the
        instructions for the LGPL more accurate -- thanks to Karl for pointing 
the
        problems out to me.  I made some other small tweaks while I was at it,
        though.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-howto.html?cvsroot=www&r1=1.17&r2=1.18

Patches:
Index: gpl-howto.html
===================================================================
RCS file: /web/www/www/licenses/gpl-howto.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gpl-howto.html      9 Jul 2007 23:32:41 -0000       1.17
+++ gpl-howto.html      12 Jul 2007 15:56:53 -0000      1.18
@@ -6,17 +6,15 @@
 <h2>How to use the GPL or LGPL</h2>
 
 <p>
-This is a brief explanation of how to place a program under the GNU
-General Public License or the Lesser General Public License.  (The
-Lesser GPL, also called the LGPL, has superseded the Library GPL,
-which was also called the LGPL.)  If you are looking for more detailed
-information, consider perusing our list of
-<a href="/licenses/gpl-faq.html">frequently-asked questions about the GNU
-General Public License</a>.</p>
+This is a brief explanation of how to place a program under the GNU General
+Public License or the Lesser General Public License.  If you are looking
+for more detailed information, consider perusing our list of <a
+href="/licenses/gpl-faq.html">frequently-asked questions about our
+licenses</a>.</p>
 
 <p>If you are considering using the GNU Lesser General Public License,
 please read the article &ldquo;<a
-href="/licenses/why-not-lgpl.html">Why you shouldn't use the Library GPL
+href="/licenses/why-not-lgpl.html">Why you shouldn't use the LGPL
 for your next library</a>&rdquo; first.  The article explains why it may
 be better to use the ordinary GPL instead, and how we would make the
 decision.</p>
@@ -44,12 +42,17 @@
 
 <p>
 You should also include a copy of the license itself somewhere in the
-distribution of your program.  In GNU programs the license is usually
-in a file called COPYING; it should be the plain ASCII text version of
-the license.  Use either
-<a href="/licenses/gpl.txt">the text version of the
-GPL</a> or <a href="/licenses/lgpl.txt">the text
-version Lesser GPL</a>.</p>
+distribution of your program.  All programs, whether they are released
+under the GPL or LGPL, should include <a href="/licenses/gpl.txt">the text
+version of the GPL</a>.  In GNU programs the license is usually in a file
+called COPYING.</p>
+
+<p>If you are releasing your program under the LGPL, you should also
+include <a href="/licenses/lgpl.txt">the text version of the LGPL</a>,
+usually in a file called COPYING.LESSER.  Please note that, since the
+LGPL is a set of additional permissions on top of the GPL, it's important
+to include both licenses so users have all the materials they need to
+understand their rights.</p>
 
 <p>
 If you have copied code from other programs covered by the same license,
@@ -112,7 +115,7 @@
 For interactive programs, it is usually a good idea to make the
 program print out a brief notice about copyright and copying
 permission when it starts up.  See
-<a href="/licenses/gpl.html#SEC4">the end of the GNU
+<a href="/licenses/gpl-3.0.html#howto">the end of the GNU
 GPL</a> for more information about this.</p>
 
 <p>
@@ -185,7 +188,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2007/07/09 23:32:41 $
+$Date: 2007/07/12 15:56:53 $
 <!-- timestamp end -->
 </p>
 </div>