Lists Home |
Date Index |
As the discussion has gone on,
it is turning out quite interesting :
The GPL will cover such intensive usages of GCC as
derived works. Passing compiler data into another
process that just continues working on it will be a
extension of the compiler.
That is a synopsis of the option from stallman and
This has a great effect on Dual Licenced code,
as soon as you start creating derived works that are
derived from GPL, you cannot free that licence for
usage in the more permissive licence.
That is the GNU side of the story.
Please read the threads on perl monks :
or on the
gcc mailing list :
The implications for many of the current programs that
would be invalidated by such tightening of the
Dual-Licence usage are scary.
--- Michael Brennan <Michael_Brennan@Allegis.com>
> > From: James Michael DuPont
> > XML-RPC and Soap are just two ways to invoke
> > Currently I am using a patched version of the
> > Compiler that streams the XML into a perl script
> via a
> > PIPE using POPEN.
> > This causes all types of problems with the GPL
> > just wanted to bring that up here and see if you
> > anything to say.
> I've been thinking for awhile that GPL's whole
> notion of "linking" is
> archaic with modern software architectures. I
> see how it is really
> tenable. LGPL seems only slightly better.
> GPL with library exception seems reasonable,
> However, I'm no expert
> with this, and it's not clear to me what
> differences there are
> between GPL with library exception and the Mozilla
> Public License (other
> than the political manifesto that the former
> includes in its license).
James Michael DuPont
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!