Re: preferred default JRE (was: Bug#411692: bootchart-view: Needs libgtkpeer.so when converting a bootchart to EPS or PNG format)
Michael Koch <konqueror <at> gmx.de> writes:
>
> On Tue, Feb 27, 2007 at 02:02:35PM +0000, Jörg Sommer wrote:
> > Hi Michael,
> >
> > Michael Koch <konqueror <at> gmx.de> wrote:
> > > Kaffe is outdated and needs some serious updates. Its better not to use
> > > it in current state. The other runtimes are more uptodate.
> > >
> > > Sablevm is even more outdated and I dont see anyone working on it at
> > > all in Debian.
> > >
> > > Recommending those two currently is like moving the user into a really
> > > wacky house.
> >
> > Interessting. Sometimes ago you suggested to use kaffe as the default JRE
> > to make things more reproducible. Now, things may have changed. What
> > should I now put in the Dependends line as prefered JRE?
> >
> > gcj | java-runtime | java2-runtime
> >
> > Which JDK should I use for building? gcj? Currently I use kaffe.
>
> Things change over time.
>
> java-gcj-compat or java-gcj-compat-dev depending on if you need JRE or a
> JDK replacement.
To explain it in a simple fashion, Kaffe hasn't seen a release in last year due
to a fair bit of work going into making it really work with an installed GNU
Classpath, rather than having to have its own slightly modified copy of GNU
Classpath installed, like it did in 1.1.7, and the usual conflict between bugs,
and available time & fighting spirit to fix them, as I personally focused more
on the soft issues around opening Sun's implementation myself, rather than
hacking on Kaffe, and just recently jumped in to do a bit of fastjar
maintenance, as that was one more fire to fight.
So we (man-di & me, wearing my Kaffe maintainer hat) have agreed to recommend
gcj over kaffe as the preferred runtime for the time being a while ago. I don't
think we really communicated that other than on IRC, though.
Reply to: