www/licenses gpl-faq.html

[Zoe]

CVSROOT:        /web/www
Module name:    www
Changes by:     Zoe <zoe>       23/03/01 11:48:19

Modified files:
        licenses       : gpl-faq.html 

Log message:
        Summary: Combining AGPLGPL linking questions into one

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

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.266
retrieving revision 1.267
diff -u -b -r1.266 -r1.267
--- gpl-faq.html        25 Feb 2023 11:30:14 -0000      1.266
+++ gpl-faq.html        1 Mar 2023 16:48:17 -0000       1.267
@@ -668,14 +668,8 @@
     <li><a href="#SystemLibraryException">Can I link a GPL program with
     a proprietary system library?</a></li>
 
-    <li><a href="#AGPLPL">Can I link GPLv3-covered modules and
-    AGPLv3-covered modules into one executable?</a></li>
-
-    <li><a href="#AGPLLibrary">Can I link a GPLv3-covered program with
-    an AGPLv3-covered library?</a></li>
-
-    <li><a href="#AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
-    a GPLv3-covered library?</a></li>
+    <li><a href="#AGPLGPL">In what ways can I link or
+    combine AGPLv3-covered and GPLv3-covered code?</a></li>
 
     <li><a href="#GPLIncompatibleLibs">What legal issues come up if I
     use GPL-incompatible libraries with GPL software?</a></li>
@@ -1323,37 +1317,17 @@
 issue slightly differently, near the end of section 3.</p>
 </dd>
 
-<dt id="AGPLGPL">Can I link GPLv3-covered modules and
-    AGPLv3-covered modules into one executable?
+<dt id="AGPLGPL">In what ways can I link or combine
+AGPLv3-covered and GPLv3-covered code?
  <span class="anchor-reference-id">(<a
 href="#AGPLGPL">#AGPLGPL</a>)</span></dt>
 <dd><p>
-You can always link GPLv3-covered modules with AGPLv3-covered modules.
-That is because each of these licenses explicitly permits linking with
-code under the other license.</p>
-</dd>
-
-<dt id="AGPLLibrary">Can I link a GPLv3-covered program with
-    an AGPLv3-covered library?
- <span class="anchor-reference-id">(<a
-href="#AGPLLibrary">#AGPLLibrary</a>)</span></dt>
-<dd><p>
-You can always <a href="#AGPLGPL">link GPLv3-covered modules with
-AGPLv3-covered modules</a>.  That is true regardless of whether some of
-the modules are libraries.</p>
+Each of these licenses explicitly permits linking with code under the
+other license.  You can always link GPL3-covered modules with
+AGPL3-covered modules, and vice versa.  That is true regardless of
+whether some of the modules are libraries.</p>
 </dd>
 
-<dt id="AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
-    a GPLv3-covered library?
- <span class="anchor-reference-id">(<a
-href="#AGPLAndGPLLibrary">#AGPLAndGPLLibrary</a>)</span></dt>
-<dd><p>
-You can always <a href="#AGPLGPL">link GPLv3-covered modules with
-AGPLv3-covered modules</a>.  That is true regardless of whether some of
-the modules are libraries.</p>
-</dd>
-
-
 <dt id="GPLIncompatibleLibs">What legal issues
     come up if I use GPL-incompatible libraries with GPL software?
  <span class="anchor-reference-id">(<a href="#GPLIncompatibleLibs"
@@ -4044,7 +4018,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2023/02/25 11:30:14 $
+$Date: 2023/03/01 16:48:17 $
 <!-- timestamp end -->
 </p>
 </div>