Re: Re: GPL and LGPL linkage to Perl

So you are saying that there is nothing stopping linking of the entire GNU compiler source code via Perl, and then the releasing of a closed source code generator?

Here is a mail from joe buck from the GCC mailling list:

http://gcc.gnu.org/ml/gcc/1999-01n/msg00706.html

"I'm afraid that's exactly what RMS is extremely worried about:

specifically, that proposed changes make it easier for *proprietary*

tools to use the gcc front ends or back ends."

So GPL/PAL co-linkage allows for the turning over of the entire GPL.

Mike

updated:formatting

Comment on Re: Re: GPL and LGPL linkage to Perl

Replies are listed 'Best First'.
Re: Re: Re: GPL and LGPL linkage to Perl by Matts (Deacon) on Mar 01, 2002 at 12:11 UTC
So you are saying that there is nothing stopping linking of the entire GNU compiler source code via Perl, and then the releasing of a closed source code generator? That's not what he's saying at all. Your example is quite obviously a derived work of GPL'd software. What he's saying is that most perl modules are distributed under the dual license scheme, and so this isn't an issue for the majority of cases. However, we do need to be aware that there are some perl modules on CPAN that are just GPL'd, and are not dual licensed, so you need to be aware of those.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: GPL and LGPL linkage to Perl
by Matts (Deacon) on Mar 01, 2002 at 12:11 UTC

So you are saying that there is nothing stopping linking of the entire GNU compiler source code via Perl, and then the releasing of a closed source code generator?

That's not what he's saying at all. Your example is quite obviously a derived work of GPL'd software.

What he's saying is that most perl modules are distributed under the dual license scheme, and so this isn't an issue for the majority of cases. However, we do need to be aware that there are some perl modules on CPAN that are just GPL'd, and are not dual licensed, so you need to be aware of those.

[reply]