How does the GPL static vs. dynamic linking rule apply to interpreted languages?

Posted by ekolis on Programmers See other posts from Programmers or by ekolis
Published on 2012-10-06T17:27:13Z Indexed on 2012/10/06 21:53 UTC
Read the original article Hit count: 346

Filed under:
|

In my understanding, the GPL prohibits static linking from non-GPL code to GPL code, but permits dynamic linking from non-GPL code to GPL code. So which is it when the code in question is not linked at all because the code is written in an interpreted language (e.g. Perl)?

It would seem to be too easy to exploit the rule if it was considered dynamic linking, but on the other hand, it would also seem to be impossible to legally reference GPL code from non-GPL code if it was considered static! Compiled languages at least have a distinction between static and dynamic linking, but when all "linking" is just running scripts, it's impossible to tell what the intent is without an explicit license!

Or is my understanding of this issue incorrect, rendering the question moot? I've also heard of a "classpath exception" which involves dynamic linking; is that not part of the GPL but instead something that can be added on to it, so dynamic linking is only allowed when the license includes this exception?

© Programmers or respective owner

Related posts about licensing

Related posts about perl