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 <users.giulie...@gmail.com> 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 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); I guess someone needs to do his home work :) > > > On Tue, Jan 3, 2017 at 1:36 PM, Tone Kastlunger <users.giulie...@gmail.com > > wrote: > >> 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 of a non-lawyer :) >> >> tortoisedoc >> >> >> On Tue, Jan 3, 2017 at 12:53 PM, Slava Monich <slava.mon...@jolla.com> >> wrote: >> >>> 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> >>> http://www.ics.com/blog/changes-qt-licensing >>> >>> On Tue, Jan 3, 2017 at 11:58 AM, Tone Kastlunger < >>> users.giulie...@gmail.com> 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, 2017 at 11:46 AM, Rinigus < <rinigus....@gmail.com> >>>> rinigus....@gmail.com> wrote: >>>> >>>>> 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 terms and, as a result, has an advantage when >>>>> compared to SFOS in this case. >>>>> >>>>> Best wishes, >>>>> >>>>> Rinigus >>>>> >>>>> On Tue Jan 3 10:20:55 2017 GMT+0100, Slava Monich wrote: >>>>> > 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 that can't be >>>>> > upgraded due to licensing restrictions will stay at 5.2. >>>>> > >>>>> > Cheers, >>>>> > -Slava >>>>> > >>>>> > >>>>> > > Hello Sailors! >>>>> > > >>>>> > > As I already told you, I am working on the Berlin Vegan guide for >>>>> SailfishOS: >>>>> > > >>>>> > > <https://github.com/micuintus/harbour-Berlin-Vegan/tree/deve >>>>> lopment> >>>>> > > <https://openrepos.net/content/micuintus/berlin-vegan> >>>>> > > >>>>> > > Recently, I added a map feature to the app: >>>>> > > >>>>> > > <https://github.com/micuintus/harbour-Berlin-Vegan/issues/41> >>>>> > > >>>>> > > But to my astonishment, I realized that using QtLocation is >>>>> currently rejected >>>>> > > by the Harbour RPM validator: >>>>> > > >>>>> > >> Requires >>>>> > >> ======== >>>>> > >> ERROR [libQt5Location.so.5] Cannot require shared library: >>>>> > >> 'libQt5Location.so.5' ERROR [qt5-plugin-geoservices-osm] >>>>> Dependency not >>>>> > >> allowed >>>>> > >> ERROR [qt5-qtdeclarative-import-location] Dependency not allowed >>>>> > >> ERROR [qt5-qtlocation] Dependency not allowed >>>>> > > Can you tell me why? >>>>> > > >>>>> > > QtLocation is listed to be available here >>>>> > > >>>>> > > <https://sailfishos.org/wiki/Qt> >>>>> > > >>>>> > > and, apart from that, AFAIK Jolla was one of the main contributors >>>>> to the >>>>> > > QtLocation module. >>>>> > > >>>>> > > >>>>> > > >>>>> > > Furthermore, I noticed that some features of the QML Map object >>>>> seem to be >>>>> > > broken or missing at the moment: >>>>> > > >>>>> > > * fitViewportToMapItems() does not have an effect >>>>> > > * 'preventStealing' is not available >>>>> > > * etc. >>>>> > > >>>>> > > Will these features be available and work once Qt is updated to >>>>> 5.6? >>>>> > > Will QtLocation be allowed for harbour store apps >>>>> > > once Qt 5.6 is (officially) available for Sailfish? >>>>> > > >>>>> > > And when can I expect Qt 5.6 to be released for SailfishOS? ;) >>>>> > > >>>>> > > Cheers, >>>>> > > micu >>>>> > > >>>>> > > PS: Happy new year to everyone! >>>>> > >>>>> > _______________________________________________ >>>>> > SailfishOS.org Devel mailing list >>>>> > To unsubscribe, please send a mail to >>>>> <devel-unsubscribe@lists.sailfi>devel-unsubscr...@lists.sailfishos.or >>>>> _______________________________________________ >>>>> SailfishOS.org Devel mailing list >>>>> To unsubscribe, please send a mail to <devel-unsubscribe@lists.sailfi> >>>>> devel-unsubscr...@lists.sailfishos.org >>>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> SailfishOS.org Devel mailing list >>> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org >>> >>> >>> >>> _______________________________________________ >>> SailfishOS.org Devel mailing list >>> To unsubscribe, please send a mail to devel-unsubscribe@lists.sailfi >>> shos.org >>> >> >> >
_______________________________________________ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
