[Marble-devel] GeoClue licence change

[Blasche Alexander]

Hi,

A DBus dependency would be acceptable from QtLocation perspective. After all it would be limited to the plug-in and not the entire library. It would be enabled based on compile tests.

In a sense geoclue is in the same situation. They want to use another library which forces them towards GPL. I somehow doubt that raising the voice would prevent it if the pull for the 3rdparty code is strong enough.

--
Alex

________________________________________
From: John Layt [johnlayt at googlemail.com] on behalf of John Layt [jlayt at kde.org]
Sent: Tuesday, August 20, 2013 20:13
To: marble-devel at kde.org; Blasche Alexander
Subject: GeoClue licence change

Hi,

Further to the recent announcement of GeoClue 2.0, I've just seen that they
have decided to re-licence from LGPLv2+ to be GPLv2+.  As far as I'm aware
this will mean we cannot use the GeoClue2 C api in QtLocation or libmarble,
and instead can only use it via DBus.

A quick look at the code bases suggests QtLocation directly links to the
library, but Marble uses the DBus interface.  As far as I know a DBus
dependency is not acceptable for a Qt Essentials module?

If we want to ever use the GeoClue2 C library directly then I suggest we
object loudly now while we still can.

Cheers!

John.