[postgis-tickets] r15642 - #3606, CGAL/SFCGAL/PostGIS License Implications Clarification Documentation

[Paul Ramsey]

Author: pramsey
Date: 2017-09-06 13:14:06 -0700 (Wed, 06 Sep 2017)
New Revision: 15642

Modified:
   trunk/doc/faq.xml
Log:
#3606, CGAL/SFCGAL/PostGIS License Implications Clarification Documentation


Modified: trunk/doc/faq.xml
===================================================================
--- trunk/doc/faq.xml	2017-09-06 19:57:24 UTC (rev 15641)
+++ trunk/doc/faq.xml	2017-09-06 20:14:06 UTC (rev 15642)
@@ -398,8 +398,9 @@
       </question>
 
       <answer>
-        <para>Almost certainly not. As an example, consider Oracle database running on Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS database as much as it wants and be under any license you like.</para>
-				<para>The only exception would be if you made changes to the PostGIS source code, and distributed your changed version of PostGIS. In that case you would have to share the code of your changed PostGIS (but not the code of applications running on top of it). Even in this limited case, you would still only have to distribute source code to people you distributed binaries to. The GPL does not require that you <emphasis>publish</emphasis> your source code, only that you share it with people you give binaries to.</para>
+        <para>Almost certainly not. As an example, consider Oracle database running on Linux. Linux is GPL, Oracle is not: does Oracle running on Linux have to be distributed using the GPL? No. Similarly your software can use a PostgreSQL/PostGIS database as much as it wants and be under any license you like.</para>
+				<para>The only exception would be if you made changes to the PostGIS source code, and <emphasis>distributed your changed version</emphasis> of PostGIS. In that case you would have to share the code of your changed PostGIS (but not the code of applications running on top of it). Even in this limited case, you would still only have to distribute source code to people you distributed binaries to. The GPL does not require that you <emphasis>publish</emphasis> your source code, only that you share it with people you give binaries to.</para>
+        <para>The above remains true even if you use PostGIS in conjunction with the optional CGAL-enabled functions. Portions of CGAL are GPL, but so is all of PostGIS already: using CGAL does not make PostGIS any more GPL than it was to start with.</para>
       </answer>
     </qandaentry>