www-commits
[Top][All Lists]
Advanced

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

www/licenses gpl-faq.html


From: Richard M. Stallman
Subject: www/licenses gpl-faq.html
Date: Fri, 27 Jun 2014 13:34:02 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       14/06/27 13:34:02

Modified files:
        licenses       : gpl-faq.html 

Log message:
        Clarify wording about requirement on license of plug-in.

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

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.200
retrieving revision 1.201
diff -u -b -r1.200 -r1.201
--- gpl-faq.html        26 Jun 2014 20:13:56 -0000      1.200
+++ gpl-faq.html        27 Jun 2014 13:34:00 -0000      1.201
@@ -1657,9 +1657,9 @@
 eliminates the problem.</p></dd>
 
 
-<dt id="GPLAndPlugins">If a program
-  released under the GPL uses plug-ins, what are the requirements for
-  the licenses of a plug-in?
+<dt id="GPLAndPlugins">If I write a plug-in to use with a GPL-covered
+  program, what requirements does that impose on the licenses I can
+  use for distributing my plug-in?
  <span class="anchor-reference-id">(<a href="#GPLAndPlugins"
  >#GPLAndPlugins</a>)</span></dt>
 <dd><p>
@@ -1671,10 +1671,9 @@
 <p>If the program dynamically links plug-ins, and they make function
 calls to each other and share data structures, we believe they form a
 single program, which must be treated as an extension of both the main
-program and the plug-ins.  This means the plug-ins must be released
-under the GPL or a GPL-compatible free software license, and that the
-terms of the GPL must be followed when those plug-ins are
-distributed.</p>
+program and the plug-ins.  This means you must license the plug-in
+under the GPL or a GPL-compatible free software license and distribute
+it with source code in a GPL-compliant way.</p>
 
 <p>If the program dynamically links plug-ins, but the communication
 between them is limited to invoking the &lsquo;main&rsquo; function of
@@ -3780,7 +3779,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/06/26 20:13:56 $
+$Date: 2014/06/27 13:34:00 $
 <!-- timestamp end -->
 </p>
 </div>



reply via email to

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