Bug report #3432
License conflict with GPLv3+ libs
|Affected QGIS version:||Regression?:||No|
|Operating System:||All||Easy fix?:||No|
|Pull Request or Patch supplied:||Resolution:||wontfix|
|Crashes QGIS or corrupts data:||Copied to github as #:||13492|
QGIS currently links two libraries, that are incompatible with QGIS' GPLv2+:
- Libspatialite (GPLv3+)
- Sqlanywhere (GPLv3+)
Linking a GPLv2+ program to GPLv3 libraries requires a switch to GPLv3+, as far as I can see.
#1 Updated by Marco Hugentobler almost 12 years ago
Hm, my interpretation from http://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility is that it should be possible:
'Is GPLv3 compatible with GPLv2? No ... However, if code is released under GPL “version 2 or later,” that is compatible with GPLv3 because GPLv3 is one of the options it permits '
#5 Updated by Volker Fröhlich almost 12 years ago
libpal's version in Trunk is also GPLv3+, according to the headers.
The website states LPGL3, maybe they changed it for newer versions. If pal was only linked, it would be OK with GPLv2+.
But as far as I know, it was changed and changes did not go upstream. I'll try to help with that, as time allows.
#7 Updated by Tim Sutton almost 12 years ago
Replying to [comment:4 pcav]:
Can anyone confirm this? Is so, I think we should drop SQLAnywhere support before releasing 1.7
Please note this was discussed in a private thread with the plugin developer before he contributed the code. I encouraged Dave to hold the discussions publicly which he did as soon as their lawyers gave the go ahead.
As Marco mentions above, our understanding is that it is ok for GPL v2 code to link to and include code with a later version of the GPL license.
Sybase have really gone out of their way to contribute their code the 'right' way and removing their plugin would not be a very generous or sympathetic move on our part.
It is our hope that Sybase's intiative may spur other proprietary geospatial database developers to copy suite and contribute open source client software for their systems. This would go a long way towards getting QGIS into the enterprise.
We are not licensing gurus, but lets find a way to make this work if there is a bona fide issue.
#8 Updated by Marco Hugentobler over 11 years ago
I still think it is no problem, because the QGIS code is under GPL2+. The important thing is the distribution of the program. It says in the header files:
"you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version". So if you are building packages (e.g. for Fedora), you redistribute them under GPL3 (any later version) and it should be ok.