Yes. It's not necessary, though, afaik, simply depending on
java-virtual-machine/java2-runtime should do the trick as
well, as the non-free
VMs should provide that just like the free VMs.
Excelent. That is what i was wanting to know. :)
Long ago with the dreaded 'eclipse running illegally on kaffe' thread (which
was complete nonsense), started out with a message that seemed to indicate
that the runtime depends would be on kaffe itself rather than a virtual
package.
From http://www.backports.org/~mkoch/unstable/ eclipse_3.1-10.diff.gz it
appears that first the (bootstrap) ecj compiler is built using gcj, then
the rest of eclipse is compiled with the natively compiled bootstrap ecj.
Ok. The natively compiled ecj, does this then compile a non-native ecj? If
so that kind of reminds me of the gcc boostrapping.
Anyway thanks.
Btw. Is there any good reason why sun-j2re1.5 (as created by make-jpkg)
provides 'java-common', when java common is a real package containing
documentation and IIRC the java policy? I'm fairly sure that sun-j2re1.5
does not actually contain this documentation. Also i doubt that all programs
handle the case where a package is both a virtual and real package at the
same time. Even worse is that some programs probably assume it is not
possible that two versions of a package (except for virtual packages) can be
installed at once. In this case to versions of a package are installed, and
the package is only somewhat virtual.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
