Hallo Roman,
* Roman Kennke wrote:
>the eclipse-platform package seems to be the only eclipse-related
>package that directly depends on non-free stuff, holding all the eclipse
>packages in contrib.
Nope: libswt2.1-motif-java also depends on a non-free lib (motif) and I
don't plan to split the packages before 3.0 (which started to be a
real mess with this "nice" build system of eclipse).
Also, the package does not completly build from source, there are
missing dependencies, which are not packaged for debian: IBM
maintainance stream of xerces (goes away in 3.0), a special version of
tomcat (we will have to do something about this in 3.0) and now ant
1.5 (which is going to be 1.6 in the 3.0 stream). Also the new OSGi
framework does not run on any free JVM (yet :).
>Is there a specific reason, why eclipse-platform does not depend on
>kaffe?
Aehm yes. I've started to experiment with kaffe and so far runs quite
well. Unfortunatelly it produces several exceptions with external
plugins. (And i haven't tested all the functionality). All in all I do
think that eclipse is a application which should be started in the
morning and stoped when going home form work. Right now I don't think
that kaffe will deliver this with all the plugins.
If you want to have eclipse installed without a non-free JVM, please
provide a dummy package (with equivs or so) for java2-runtime and it
should work.
>suppose the eclipse-sdk uses eclipse-platform stuff and when running the
>SDK with kaffe, the platform stuff also is loaded by kaffe. Right?
the sdk package is only there to pull in the same functionality than
the upstream SDK drops. eclipse platform has the starter and so it
depends on a JVM.
Jan
--
Jan Schulz [EMAIL PROTECTED]
"Wer nicht fragt, bleibt dumm."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
