Iñigo Figuero wrote:That license applies to distribution, not for use, I think.
i thing you are referring to
sect.2 of pt.0 in the GPL:
" Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted,...". yes, that's true, and the general aim of this license is indeed focused on maximizing the "freedom" of users resp. to protect it...
but using GPL licensed plugins in closed source applications is a very special case. it will be treated like dynamic linking of libraries. the GPL FAQ clearly states
about this case:
"If the main program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single combined program, which must be treated as an extension of both the main program and the plug-ins."and the consequences are explained
two paragraphs later under
"Can I apply the GPL when writing a plug-in for a nonfree program?":
"If they form a single combined program this means that combination of the GPL-covered plug-in with the nonfree main program would violate the GPL. However, you can resolve that legal problem by adding an exception to your plug-in's license, giving permission to link it with the nonfree main program."but i still have to remark again, that the GPL was invented to protect the freedem of users and not to restrict them by unnecessary rigorousness. nevertheless we still should try to respect this general rules behind free software not less than all those licensing restrictions and access barriers in the commercial world.
Posted: Wed Sep 19, 2018 8:24 pm