Re: eight packages could possibly go to main!
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/debian-legal-200311/msg00012.html
FSF's stand on using GPLed interpreters/class libraries to run applications:
http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
Of course, the definitive text to read is the GPL itself, not because Kaffe
is GPLed, but because its class libraries are. It could be argued that, even
if its class libraries were not GPLed, the combination of Kaffe and its libraries
should be, as a JVM does link with its class libraries at run time.
I repeat: I am simply pointing you to the relevant documentation, but I am not
willing to discuss the issue. If you wish to discuss it, please send your
questions to debian-legal which is the appropriate forum for this.
Have fun!
Etienne
Daniel Bonniot 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 JDK" in
particular? If so, then is it really an issue in practice? As far as I
know, Kaffe is not trying to introduce unique features, so it would be
surprising that any application can be build/run _only_ with Kaffe.
If you mean "the only free JVM that can build/run it is Kaffe", then
that becomes a more likely situation, but then I don't see the reasoning
why the license of the app would need to be GPL compatible.
Daniel
--
Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/
SableVM: http://www.sablevm.org/
SableCC: http://www.sablecc.org/
Reply to: