The description for this package states that it is '32bit version Sun's J2SE Development Kit' which is quite misleading. Betelgeuse said in IRC that it should be pretty easy to just ship the JDK instead of the JRE but WITHOUT shipping the usual entry into /etc which lets the build system know that a JDK is available. This lets us run Google Web Toolkit (which ships 32-bit libs, unavoidable presently) natively without all kinds of java-config musical chairs. Thanks! Reproducible: Always
there are no headers for jni, so this package really looks like jre rather then jdk.
No tools.jar either, I agree that this is a JRE. I am requesting that we package the JDK instead. I don't want this new emul- package to be a "real" JDK in the Gentoo way though, as having it as an available system vm could cause a lot of pain.. Thanks!
I fixed the descriptions in CVS. I'm closing the bug as WONTFIX but feel free to reopen it if you manage to make a emul-linux package for a full JDK.
Serkan: I think WONTFIX is nor appropriate, ebuild requests should stay open just have enhancement severity. So reopening. And I think we want to limit the usage as a build VM (when emerging java stuff), not as system VM (unless you meant the same and just used wrong word, common mistake :) Heck even the current emul JRE packages can be selected as system VM currently, and there have been no confused bug reports about it yet.
*** Bug 217267 has been marked as a duplicate of this bug. ***
*** Bug 271798 has been marked as a duplicate of this bug. ***
I care about this less and less since GWT no longer requires a 32-bit JDK, this is since the GWT-2.0 milestone # 1 (we're now on ms-2). The bug has been open for over a year with no movement, I suggest closing it.
64-bit JDK is optimized for servers and has much higher memory consumption than 32-bit JDK. It is better to use 32-bit JDK on 64-bit desktops.
I don't think the people at Google give a damn. I do not work for them, but I do work with many of them in ##gwt and I can state with a lot of confidence that since this issue is resolved with their CURRENT release (2.0.0; released a couple of weeks ago) and all other releases are essentially deprecated (see what I've dubbed "The Great Ticket Closing Blizzard of 2009" where Google is deprecating all open tickets which are open for a year or more without any movement). Anyhow, this has absolutely no traction with Google. And it seems a waste of our resource to try and fix this if GWT is our only aim (which was why I originally opened it, anyhow). I would like to close this as WONTFIX since the GWT issue is resolved, please re-open it if you are willing to take it over; I am going to mute the thread in GMail.
