4 ms·
How exactly does that work, what if the plugin was created before the program?
by Drakim 5y ago
How exactly does that work, what if the plugin was created before the program?
- deleted 5y ago[deleted]
- wolrah 5y agoThe theoretical dividing line (I don't think this has ever gone to court) is whether the plugin interface is specific to the GPL application. The prevailing view is that if a GPL application is just implementing a pre-existing plugin API (for example VST or NPAPI) then obviously plugins built for that API can't be held to the licensing of one particular host application. On the other hand, if said API is specific to the GPL application then the GPL applies (for example Linux kernel device driver interfaces). I'm not sure if it's ever even happened, but it's interesting to contemplate the possibility of a proprietary application implementing compatibility with an existing GPL app's plugin API.
- bombcar 5y agoIt’s down to the definition of “derivative work” and the FSF may not have it legally correct (they may be overstating what can be considered derivative from a legal viewpoint) - as it has never reached litigation we don’t have a final solid answer. And even if it did we’d only have a precedent that may be hard to apply.