www/licenses gpl-faq.html

[Brett Smith]

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

Modified files:
        licenses       : gpl-faq.html 

Log message:
        Add more detailed rules in #WindowsRuntimeAndGPL.
        
        Apparently it's common for Windows runtime libraries to be distributed
        with the programs that use them, so the previous version of the FAQ
        created some confusion.  This new answer is meant to be more explicit
        about the boundaries of what is and isn't allowed.  Approved by RMS;
        see #716422 and #704291.

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

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -b -r1.171 -r1.172
--- gpl-faq.html        15 Nov 2011 05:44:48 -0000      1.171
+++ gpl-faq.html        12 Dec 2011 19:07:10 -0000      1.172
@@ -551,7 +551,7 @@
     <li><a href="#WindowsRuntimeAndGPL">I'm writing a Windows
     application with Microsoft Visual C++ and I will be releasing it
     under the GPL.  Is dynamically linking my program with the Visual
-    C++ run-time library permitted under the GPL?</a></li>
+    C++ runtime library permitted under the GPL?</a></li>
   
     <li><a href="#MoneyGuzzlerInc">I'd like to modify GPL-covered
     programs and link them with the portability libraries from Money
@@ -1489,22 +1489,32 @@
 
 
 <dt id="WindowsRuntimeAndGPL">I'm writing a Windows application with
-    Microsoft Visual C++ (or Visual Basic) and I will be releasing it
-    under the GPL.  Is dynamically linking my program with the Visual
-    C++ (or Visual Basic) run-time library permitted under the GPL?
- <span class="anchor-reference-id">(<a href="#WindowsRuntimeAndGPL"
- >#WindowsRuntimeAndGPL</a>)</span></dt>
-<dd><p>
-The GPL permits this because that run-time library normally accompanies
-the compiler or interpreter you are using.  The run-time libraries here are
-&ldquo;System Libraries&rdquo; as GPLv3 defines them, and as such they are
-not considered part of the Corresponding Source.  GPLv2 has a similar
+Microsoft Visual C++ (or Visual Basic) and I will be releasing it
+under the GPL. Is dynamically linking my program with the Visual
+C++ (or Visual Basic) runtime library permitted under the GPL?
+<span class="anchor-reference-id">(<a href="#WindowsRuntimeAndGPL"
+>#WindowsRuntimeAndGPL</a>)</span></dt>
+
+<dd><p>You may link your program to these libraries, and distribute
+the compiled program to others. When you do this, the runtime
+libraries are &ldquo;System Libraries&rdquo; as GPLv3 defines them.
+That means that you don't need to worry about including their source
+code with the program's Corresponding Source. GPLv2 provides a similar
 exception in section 3.</p>
 
-<p>That doesn't mean it is a good idea to write the program so that it
-only runs on Windows.  Doing so results in a program that is free
-software but &ldquo;<a href="/philosophy/java-trap.html">trapped</a>&rdquo;
-by Windows.</p></dd>
+<p>You may not distribute these libraries in compiled DLL form with
+the program. To prevent unscrupulous distributors from trying to use
+the System Library exception as a loophole, the GPL says that
+libraries can only qualify as System Libraries as long as they're not
+distributed with the program itself. If you distribute the DLLs with
+the program, they won't be eligible for this exception anymore; then
+the only way to comply with the GPL would be to provide their source
+code, which you are unable to do.</p>
+
+<p>It is possible to run free programs that only run on Windows, but
+it is not a good idea.  These programs would be
+&ldquo;<a href="/philosophy/java-trap.html">trapped</a>&rdquo; by
+Windows, and therefore contribute zero to the Free World.</p></dd>
 
 
 <dt id="OrigBSD">Why is the original BSD
@@ -3561,7 +3571,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2011/11/15 05:44:48 $
+$Date: 2011/12/12 19:07:10 $
 <!-- timestamp end -->
 </p>
 </div>