Il 31/03/20 15:35, Tuukka Turunen ha scritto:
The point of the "Prohibited combination" is to prevent a company or a chain of companies (like in a typical subcontracting scenario) from making part of the product with non-paid Qt and part with paid. Qt being as defined in the commercial license agreement, i.e. including tools and framework. This was what the person initiating this mail thread asked about. I do agree that it gets complex when one starts including items created by an independent third party. This is at the moment not listed as an allowed case, even though it is not something we specifically aimed to prevent.
I understand the underlying reasoning 100%, but clarity is important here, and the ones I brought forward aren't some "far fetched" hypothetical scenarios.
In a product developed with Qt commercial, anyone is going to using a bunch of non-Qt libraries, for instance coming with any basic Linux installation (e.g. glibc, libstdc++, ICU, whatever). Maybe some ad-hoc ones, e.g. Boost. How can one be sure that none of those has been developed using GPL Qt Creator? Should one just "live with" the possibility of infringing the commercial license, because TQC is just not interested at chasing this case down?
Thakns, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: Firma crittografica S/MIME
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
