Any plan for upgrading Qt version?

[olf]

@ahjolinna

looking to the QtWayland licensing part at github it does have LGPLv3 as an option: qtwayland/LICENSES at dev · qt/qtwayland · GitHub

… since QT 6.4, but not before that if you look closely.

anyway, what I understand the original plan was to upgrade to Qt5.15.x but as the porting process was so slow and Qt6 is now more mature they seem to have moving to it instead …(at least when looking on some of the work at [SailfishOS@GitHub], they did start port stuff to 5.15.x and now there is work towards 6.x)

Can you please provide specific pointers (i.e., web-links) to what you mean / saw: I cannot find any newer Qt-version imported there by sailors after their long stalled Qt 5.9 efforts at SailfishOS@GitHub.

@attah

Interesting. I wonder if QtWayland reverted back to allowing LGPL silently. GPL-only there would indeed have been a potential blocker (but the ~5.9 effort surely was aborted before that license change).

Looking at the Qt’s official documentation there is no “licence change” for QtWayland in Qt 6 (and sure not for it in Qt 5).

See also Qt company’s nicely parametrisable licensing overview for all Qt components, which states just the same: No license change for QtWayland, it is GPLv3-only since Qt 5.7 for all non-commercial licenses.

@attah

My best-guess was always that the anti-tivolizarion in LGPL3 was a big risk for being able to lock bootloaders and sign stuff in commercial projects. This was somewhat corroborated by abr’s recent talk, iirc.
My memory fails me on where exactly that was… i’ll see if it comes back to me later and edit that in.

Which abr’s talk where? Any reference / link?

BTW, the whole topic was discussed in depth at TMO in October 2020 in the thread Qt “stuck” at v5.6 in SailfishOS. Core excerpt:

[…] because [the *GPLv3 licenses] consistently use the term “user” (instead of “licensee” etc. as all other FLOSS licenses do, including the *GPLv2s), plus one must provide the “user” with full control over the *GPLv3 software (the “Anti-TiVO paragraph”) including the ability to alter it anytime at free will.
This renders *GPLv3 licensed software unsuitable for devices which are not user-controlled, e.g., MDM-managed devices in a company or government office, and generally any device, whose user is not its owner (specifically when the right to use and the right of possession are both transferred to a user).