|The stupid question is the question not asked|
GPL and LGPL linkage to Perlby mdupont (Scribe)
|on Feb 28, 2002 at 09:16 UTC||Need Help??|
For the past three years, I have been working on a project to create a object oriented interface to the GCC compiler, the GCC Node Introspector.
This turned into a perl project after realising the power of perl for handling strings and complex data structures. Also the number of tools that link into perl are amazing.
This linking of programs can to GPL code can be very tricky, and full of problems as a detailed review of the GPL and LGPL can point out.
In this meditation, I will point out what I see as some bumpy spots for Perl and GPL, and clauses that might have been overlooked for too long.
Let us review the the GPL and its implications for linking to Perl :
GPL<quote> This General Public License does not permit incorporating your program into proprietary programs.
If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library.
If this is what you want to do, use the GNU Library General Public License instead of this License.
GPL Commentincorporating is a term that implies to me containment,
If I write a proprietary program that uses the output of the GPL Code is that containment?
If I open the a pipe to another program, and call functions in it using data from a GPL program, is that not what a linker does, but via a different method?
Lets look at the LGPL 2.1<quote>We use this license for certain libraries in order to permit linking those libraries into non-free programs.
When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library.
The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom.
The Lesser General Public License permits more lax criteria for linking other code with the library.
LGPL CommentNow this does not cover linking via RPC/IPC or Shared Memory or File.
Let alone CORBA or XML-RPC/SOAP.
This comes done to the definition of linking, is linking only with the linker, or is linking a method of passing data between function calls?
Can I call a GPLed Function in GIMP via a perl script webpage, but I cannot link to it?
LGPL part 2<quote> 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. <quote>
LGPL Comment part 2distribution conditions are incompatible with these Does that cover PAL which gives you more freedom. Can I link via perl and all of a sudden, there is no more GPL?
By these terms, every perl script which links in with GPLed GIMP via script would require such permission to be asked.
As you can see, the network has changed the meaning of linking.
(Updated to add a readmore, better formatting and an introduction.)