3 ms·
If it's a plugin that's distributed separately from the base application I suspect you would only have to release the source to the actual plugin. Look at it t
by tlrobinson 19y ago
If it's a plugin that's distributed separately from the base application I suspect you would only have to release the source to the actual plugin.
Look at it this way: Photoshop is a proprietary application, but anyone can write a plugin. If someone wrote a Photoshop plugin using GPL'd software and distributed it independently, Adobe would not have to GPL all of Photoshop. They would have to release the source code to the plugin, of course.
That said, if the only reason the piece of software is written as a plugin is to circumvent the GPL, you'll piss off a lot of people. (e.x. the Acquisition LimeWire client for OS X)
- cstejerean 19y agoIf Adobe distributes Photoshop and the plugin together they will likely be violating the GPL (see the GPL FAQ). I think it's only OK to use GPL plugins in non-GPL software if the GPL plugins are distributed separately by a third party (but then again I'm not a laywer).
- tlrobinson 19y ago"plugin that's distributed separately" "distributed it independently"