|
|
|
|
|
by pie_flavor
1320 days ago
|
|
It is impossible to tell, from this post, whether you mean to say that the teeth can be removed from the GPL by simply licensing a dependent work as LGPL, or whether you mean to say that the GPL does not steal ownership from you and you can adapt it later to be non-GPL. If the former, this is laughably wrong and displays a complete misunderstanding of open source licensure. The GPL infects the entire project, that's its defining factor, and you cannot set the entire work's license as LGPL any more than you can set it as MIT. If the latter, this is a fake distinction, and displays dishonesty about the risks. Regardless of what license I can distribute my code under later if I change it, in order to use a GPL-covered library I must license the version of my code that depends on it under the GPL. That version of the code will be GPL-licensed to anyone that has it, for eternity; I cannot retract it, regardless of what changes I make to my own copy. Either way this is not a reassuring post. I am glad to know Slint is GPL so I can stay far away from it and recommend others do the same. |
|