I wouldn't say essentially LGPL. The thing is that when PostGIS is used, it is via linking or the psql and similar driver API. So e.g. PostgreSQL can exist without PostGIS and your software can call PostGIS functions without embedding PostGIS into it and alls stored functions are in source code anyway if you sell to a customer.
It falls under this exception: https://www.gnu.org/licenses/gpl-faq.html#SystemLibraryException Now if you were to take the source code of PostGIS and compile it into your own software, then your software I think would then be governed by the https://www.gnu.org/licenses/gpl-faq.en.html#IfLibraryIsGPL you describe. Just my two cents, Regina -----Original Message----- From: postgis-users [mailto:[email protected]] On Behalf Of Bruce Momjian Sent: Wednesday, December 21, 2016 1:29 PM To: [email protected] Subject: [postgis-users] Is PostGIS effectively LGPL? I know PostGIS is GPL licensed. However, I thought the major difference between the GPL and the LGPL was that the LGPL didn't require applications that link with the LGPL software to honor the LGPL requirements. Since PostGIS doesn't force applications that link to PostGIS to honor the GPL license, isn't PostGIS more like LGPL than GPL? Here is the linking exception in the PostGIS FAQ: http://postgis.net/docs/manual-dev/PostGIS_FAQ.html#license_faq FYI, This differs from the Free Software Foundation's interpretation of the GPL linking/license-transfer requirement: https://www.gnu.org/licenses/gpl-faq.en.html#IfLibraryIsGPL -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + _______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/postgis-users
