Jan Schulz wrote:
Hallo Dalibor, * Dalibor Topic wrote:* figure out how you want to interpret the GPL in this case. The rest follows from that.Problems not touched: *execution* of GPL-incompatible code using GPLed libs and/or GPLed JVMs is beyond the scope of this message.Could you please take this two thing to debian-legal and get a opinionthere.
Agreed.
Anyway: if thats true, that it will kill kaffe in debian, as we could not use it with almost any programm, because in one way or another, they all include apache licensed libs (-> jakarta project).
Don't agree. ;) Even if this was true, it would be good enough for *compiling* all the GPLd java apps. I guess there must be some, judging by freshmeat:
http://freshmeat.net/browse/198/?topic_id=198&orderby=&filter=15 1051 GPLd Java apps. By far the most popular license for Java apps.As Grzegorz said, he isn't even touching *execution*, that's another field where we are bound to disagree ;)
Anyway, we're switching kaffe's class library over to GNU Classpath, which is GPL + linking exception, and that should make the people who support FSFs interpretation happy, too, as GNU Classpath explicitely allows linking to it.
The plan is to have that finished before next summer. People are always welcome to jump in and help out: merging classes is usually simpler than writing them from scratch ;)
I hate licenses...
Don't agree. GPL is quite nice for me, the trouble is that the rest of the world sometimes uses something incompatible and then we have to play lawyers to decide what's allowed and what not ;)
cheers, dalibor topic