Steve Langasek <[EMAIL PROTECTED]> writes: >> I mean, I can understand not wanting people to use GNU Readline as part of >> a GPL-incompatible app unless it in no way actually depends on it being >> GNU Readline, rather than something else with the same API. But claiming >> that a GPLed *plugin* created *after* a program with a defined plugin >> API, and after another plugin with a GPL-incompatible license, causes the >> distribution of a package of "program plus some plugins that work with it" >> to become a derived work, is just frigging silly. > > I don't believe that is the claim.
Then read the section "Can I use the GPL for a plug-in for a non-free program?" in the GPL FAQ: http://www.gnu.org/licenses/gpl-faq.html#GPLPluginsInNF If there are any other interpretations of that section, please enlighten me. -- Måns Rullgård [EMAIL PROTECTED]