license incompatibility with libgit2 ?
Submitted by Andreas Henriksson
Link to original bug (#764886)
Description
Recently looked at things related to libgit2 in Debian and noticed that I'm not sure how licenses of different components could possibly interact well.
libgit2 is GPLv2 with linking exception (for possible usage with openssl, which is currently disabled in Debian because of some GPLv2-only projects wanting to use libgit2 apparently).
libgit2-glib COPYING says LGPLv2.1 and random code sample says "or later".
gnome-builder now has git support as a separate plugin. Code is GPLv3+.
As I see it using libgit2 + libgit2-glib means you've lost the linking exception (and thus can't build with openssl enabled, since openssl license is not GPLv2-compatible IIRC) and the entire work is now basically/effectively "upgraded" to GPLv2.
Linking gnome-builder (git plugin) to it is simply not possible since GPLv2 and GPLv3 is not compatible.
One possible solution as I see it could be to relicense the git plugin to GPLv2+ (or even better LGPLv2+ to avoid loosing the openssl linking exception) and declare that gnome-builder plugins does not constitute a derived work of gnome-builder (ie. add a linking exception to gnome-builder, which might mean a complete relicensing? Could possibly be seen as just a clarification though).
Is there something I've misunderstood here? What are your take on license compatibility with gnome-builder and its dependencies?