[Top][All Lists]

[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: Wed, 03 Oct 2007 20:55:39 +0000

CVSROOT:        /webcvs/www
Module name:    www
Changes by:     Richard M. Stallman <rms>       07/10/03 20:55:39

Modified files:
        licenses       : gpl-faq.html 

Log message:
        (NFUseGPLPlugins): Explain that use of fork/exec does not override
        the significance of other communication mechanisms.


Index: gpl-faq.html
RCS file: /webcvs/www/www/licenses/gpl-faq.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -b -r1.111 -r1.112
--- gpl-faq.html        28 Aug 2007 01:29:22 -0000      1.111
+++ gpl-faq.html        3 Oct 2007 20:55:26 -0000       1.112
@@ -1461,10 +1461,11 @@
-It depends on how the program invokes its plug-ins.
-If the program uses fork and exec to invoke plug-ins, then the
-plug-ins are separate programs, so the license of the plug-in
-makes no requirements about the main program.
+It depends on how the program invokes its plug-ins.  For instance, if
+the program uses <em>only</em> simple fork and exec to invoke and
+communicate with plug-ins, then the plug-ins are separate programs, so
+the license of the plug-in makes no requirements about the main
 If the program dynamically links plug-ins, and they make function
 calls to each other and share data structures, we believe they form a
@@ -1479,6 +1480,9 @@
 with some options and waiting for it to return, that is a borderline
+Using shared memory to communicate with complex data structures
+is pretty much equivalent to dynamic linking.</p>
 See also the question <a href="#FSWithNFLibs">I am
 writing free software that uses a non-free library.</a>
@@ -3198,7 +3202,7 @@
     <!-- timestamp start -->
-    $Date: 2007/08/28 01:29:22 $
+    $Date: 2007/10/03 20:55:26 $
     <!-- timestamp end -->

reply via email to

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