And for the record, after asking around, the real reason Jolla is stuck with ancient Qt is because the QtWayland compositor module "graduated" as a non-essential Qt addon and thus changed license from a mixture of BSD+LGPL to GPL only. Only essential Qt components (like the client parts of the Wayland module) remain as LGPL. Since Silica is apparently still not fully open, this puts them in a problem as the compositor process is linking Silica and Qt Wayland Compositor together. (Plus a lot of porting to do, anyway).
[...] GPL has it's purpose and we just have realize it when the license for your code is selected. In case of Qt, it is a way to ask for commercial licenses for non-free software. So, if Jolla goes for Qt update, there maybe a problem with mixing non-free Silica with GPLv3 Qt. [...]
[...] going through https://www.qt.io/product/features#js-6-3 (LGPLv3), I can see that Qt Wayland Compositor is not compatible with it and requires GPLv3 (or "commercial"). Lipstick runs on it, but fortunately it is open-source. Not sure of the rest of the composer.[...]
[...] https://forum.sailfishos.org/t/silic...urce-code/3561
[...]my dear troll. I was still hoping for anything substancial from your side.
The issue is not related to GPLv3 at all. In fact Jolla is already shipping some GPLv3 software in the device images (at least for the original Jolla). E.g. I've just checked and GPLv3 readline is used, for example. So much for the GPLv3 FUD...
[...] IRC community meeting log of 2021-02-25 [...]