On Sat, 4 Mar 2000, David Johnson wrote: > But what does "direct functionality" mean in terms of licensing? I can see > functionality being added to a GPL application in ways that both would and > would not violate the GPL. If I wrote a new plugin for Gimp, it would add > functionality, but would only have runtime linkage. But putting the exact some > code within the body of the Gimp source code cause it to come under the purview > of the GPL. According to RMS, plugins are *also* derivative works, so both your examples would come under the GPL. (Which produces the odd result that it is legal to write a GPL plugin for Internet Explorer but not for Netscape 4, since Internet Explorer comes under the system component exception.)
- Re: How To Break The GPL W. Yip
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- Re: How To Break The GPL Jonathan Marks
- Re: How To Break The GPL David Johnson
- Re: How To Break The GPL Mark Wells
- Re: How To Break The GPL Jonathan Marks
- Re: How To Break The GPL John Cowan
- Re: How To Break The GPL David Johnson
- Re: How To Break The GPL David Johnson
- Re: How To Break The GPL Jonathan Marks
- RE: How To Break The GPL Ken Arromdee
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- Re: How To Break The GPL Mark Wells
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- Re: How To Break The GPL John Cowan
- Re: How To Break The GPL John Cowan
- RE: How To Break The GPL Rod Dixon, J.D., LL.M.
- Re: How To Break The GPL David Johnson
- Re: How To Break The GPL Martin Konold

