I do not have time to go over this again, but here are two relevant
URLs explaining different views. The strictest view is the FSF's
interpretation of the GPL, if you care about it.
Debian Java discussion of GPLed Kaffe libraries + dependent applications:
http://lists.debian.org/debian-legal/2003/
Would the Apache license be GPL compatible in that method? All of the
Jakarta Commons for example. I did not think the GPL worked in that
fashion... for example I can create and build a non-GPL application with
GCC, right?
On Sun, 2004-02-22 at 03:45, Etienne Gagnon wrote:
> Jerry Haltom wrote:
>
Etienne Gagnon wrote:
The biggest problem is that Kaffe is licensed under the GNU GPL, so if an
application/library can only be compiled with Kaffe, it must be licensed
under the GPL too (or at least be "license compatible" with the GPL).
By "only compiled with Kaffe", you mean "and not with Sun's
Jerry Haltom wrote:
Can building these .class files built with Kaffee prevent their usage
with a non-free alternative JVM? If Kaffe is totally Java standards
compliant, then that's cool... is that the case? Will there be ANY
deficiencies in these classes by building them with Kaffee?
If so, then I
4 matches
Mail list logo
