Debian should ship the kjc source code -- I agree that should be done. It's a build dependency, and Debian should include the sources for all the build dependencies.
The kjc source code is available publicly, as are the small number of patches we applied (in the kaffe.org CVS).
What's the best way to fix it?
Dalibor just removed kjc.jar from our CVS. We were already discussing ways of redoing the build and packaging, and the bootstrapping process with kjc.jar has been painful, to say the least. So we were going to redesign the packaging process altogether anyhow.
I think I want to propose separating the whole JDK part (eg. javac and relating utils) out from Kaffe, and make the main product of Kaffe be just the JRE. Ideally, we could split off the class libraries as well, since that comes from Classpath mostly now. So the build process could be something like:
a) download Kaffe, KJC, and Classpath separately b) Run some build script which builds a JDK
That's less nice than our current solution of having one tarball that gets downloaded. But I really think Kaffe should just be the virtual machine itself, not an entire distribution.
In the meantime, can't the Debian package just be modified to include the kjc source tarball and related patches? They are available. That should fix the bug.
There should be another release of Kaffe soon, perhaps in the next month or so.
Cheers,
- Jim
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
