On Thu, 2005-13-01 at 22:51 +0100, Måns Rullgård wrote: > >> > Do you understand that a program being interpreted is effectively > >> > linked to these facilities it uses thru these bindings? > >> > >> Yes. Which bindings does Eclipse use? > > > > I told you. Plenty. And if we're making Eclipse Build-depend on > > a GPLed version of these, then we're explicitely forcing these bindings > > to be GPLed. > > Guess what, Eclipse does not have a Build-depends on any GPLd JVM. It > has a Build-depends on j2sdk1.3 | j2sdk1.4, which are virtual > packages. Guess what else, Kaffe doesn't provide either of these. > Surprised? I'm amused.
Which Eclipse packages? The old ones we have in SID now? Irrelevant. There would have been nothing whatsoever to discuss in such case. The *new* Eclipse packages that are being prepared now and which we've been discussing (I already said it in another email, but you must have crossed yours) have it this way: Build-depends: kaffe Depends: kaffe | java2-runtime [ From http://kyoto.larvalstage.net/ubuntu/warty/ ] So a user who does either 'apt-get source eclipse' or 'apt-get install eclipse' will link (either at compilation time or at runtime) to Kaffe's Java library, and to Kaffe JVM bindings which are all GPL. I hope this clarifies _at least_ this issue. GBP -- Grzegorz B. Prokopski <[EMAIL PROTECTED]> SableVM - Free, LGPL'ed Java VM http://sablevm.org Why SableVM ?!? http://sablevm.org/wiki/Features Debian GNU/Linux - the Free OS http://www.debian.org