Open rhfogh opened 5 years ago
Thanks @rhfogh for looking into this again, and this of course applies even though we are not really distributing MXCuBE as a product ? The fact that we have to pay this licensing fee have more to do with that MXCuBE would become LPGL licensed and that as nothing to do with how its distributed, except for that we cant distribute it bundled with PyQT ?
As of 20230830, it seems liek this issue is STILL not sorted.
The steps we need are clear:
Every group that develops with Qt needs a commercial license per contributing programmer.
PyQt4: 4.12.3
PyQt5: 5.15.7 - 5.19.9
PyQt6: 6.4.0 - 6.5.2 Our current license will also give us all versions released until January next year.
Could other groups comment with their current status?
As agreed in the last two meetings, we must comply with LGPL license conditions. This means that any group that is developing code that uses PyQt must have a commercial license before the code starts shipping. The cost is 450 Euro (+ VAT) as a one-off payment, for each seat. See https://www.riverbankcomputing.com/commercial/ for details.
GPhL has now bought a license; could the rest of you check whether you 1) never develop Qt-related code? 2) Already have a commercial Qt license? or 3) are going to buy one now?
The operative part of the Riverbank license FAQ is as follows - I gather we are not distributing PyQt, but having the users use their own copy:
Q. | Can my proprietary application be used with the copy of the GPL version of PyQt that the user already has installed (as part of their Linux distribution for example)?
A. | Yes, so long as you meet the following conditions:
Q. | Can I distribute my own copy of the GPL version of PyQt with my proprietary application?
A. | Yes, so long as you meet the following conditions: