Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Slava Monich
As far as I understand, QtLocation license terms have changed and that prevents it from being upgraded to 5.6 which is its first stable release. That's why it's not allowed and won't be allowed even after the rest of Qt is upgraded to 5.6. Qt 5.6 is coming with the next update. Those modules t

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Rinigus
Morning, Slava, would you mind to check out which licensing terms prevent QtLocation specifically? Or maybe someone else knows specifics? Is there any hope that the situation would change in future? I wonder whether all platforms are hit by it or whether Ubuntu Touch complies with the new ter

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Tone Kastlunger
Weird, http://doc.qt.io/qt-5/licensing.html from here only MIT / BSD-Style licenses are mentioned. Where's the issue there? tortoisedoc On Tue, Jan 3, 2017 at 11:46 AM, Rinigus wrote: > Morning, > > Slava, would you mind to check out which licensing terms prevent > QtLocation specifically? Or m

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Tone Kastlunger
Even more detailed view : http://www.ics.com/blog/changes-qt-licensing On Tue, Jan 3, 2017 at 11:58 AM, Tone Kastlunger wrote: > Weird, > http://doc.qt.io/qt-5/licensing.html from here only MIT / BSD-Style > licenses are mentioned. > Where's the issue there? > > tortoisedoc > > On Tue, Jan 3, 20

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Slava Monich
I'm not a lawyer but apparently something is fundamentally wrong with LGPLv3. This sounds similar to what I heard about it: http://nmav.gnutls.org/2013/03/the-perils-of-lgplv3.html -Slava Even more detailed view : http://www.ics.com/blog/changes-qt-licensing On Tue, Jan 3, 2017 at 11:58 AM,

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Tone Kastlunger
Doesnt Qt Provide the choice for GPLv3 / LGPLv3? >From the FSF compatibility matrix http://gplv3.fsf.org/dd3-faq it appears that only using GPLv3 library code in LGPLv2 and LGPLV2.1 is cause for trouble (=forced upgrade to GPLv3); but LGPLv3 seems ok. That said, this has been viewed with eyes o

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Tone Kastlunger
Ah! Slava, the article you pointed at is wrong; Quoting : "The same incompatibility issue exists with LGPLv2.1 projects that want to use an LGPLv3 library. They *must* be upgraded to LGPLv3. " This statement is not true for LGPLv3, but for GPLv3 (according to FSF's compatibility matrix at least);

Re: [SailfishDevel] QtLocation | Qt 5.6

2017-01-03 Thread Tone Kastlunger
The writer probably intented "to use a library" as "to copy code from a library"; Duh. On Tue, Jan 3, 2017 at 2:08 PM, Tone Kastlunger wrote: > Ah! Slava, the article you pointed at is wrong; > > Quoting : > > "The same incompatibility issue exists with LGPLv2.1 projects that want to > use an LG

Re: [SailfishDevel] QtLocation | Qt 5.6 - alternatives (PinchMap)

2017-01-03 Thread Martin Kolman
Mon, 02 Jan 2017 01:09:49 + Helicalgear .: Hi, Qt5.2 itself provided the "QtLocation" as you see. But, unfortunately, QtLocation is not allowed to use for 3rd party apps officially, right now. Please see "Sailfish FAQ" https://harbour.jolla.com/faq#QML_API And the list of modules which ca

Re: [SailfishDevel] QtLocation | Qt 5.6 - alternatives (PinchMap)

2017-01-03 Thread Peter Pykäläinen
Thanks for sharing, great info! BR, // Pete Martin Kolman kirjoitti tiistai 3. tammikuuta 2017: > Mon, 02 Jan 2017 01:09:49 + Helicalgear .: > > Hi, > > > > Qt5.2 itself provided the "QtLocation" as you see. > > But, unfortunately, QtLocation is not allowed to use for 3rd party > > apps of