Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71000 - Java 5.0 open-sourced by Sun
Summary: Java 5.0 open-sourced by Sun
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-12 13:01 UTC by Kaiting Chen
Modified: 2004-11-16 04:01 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kaiting Chen 2004-11-12 13:01:10 UTC
Sun has recently open-sourced Java 5.0 in its community source program. This means that we should now be able to compile Java 5.0. The Gentoo ebuilds have not been updated to reflect this change. Please make a Java 5.0 ebuild for sun-j2sdk.

Reproducible: Always
Steps to Reproduce:
Comment 1 Kaiting Chen 2004-11-14 16:11:35 UTC
Someone changed the severity of this bug from Blocker to Normal. Actually, by definition, it is a blocker, as it causes lack of development or testing work.
Comment 2 Saleem Abdulrasool (RETIRED) gentoo-dev 2004-11-14 17:16:18 UTC
Java 1.5 (5.0) is available in portage as it is.  The released source is still under semi-stringent terms.  I would assume a large portion of the work would still be conducted under the licence from the closed source version of Java.  As such, it does not really hinder development.

However, that is my opinion, and I agree with axxo on the relabeling.  You are, however, entitled to yours :-)
Comment 3 Kaiting Chen 2004-11-14 17:34:56 UTC
Does that mean that there is no point to compiling Java? I was under the impression that the open-sourced copy of Java could be compiled to use NPTL.
Comment 4 Jochen Maes (RETIRED) gentoo-dev 2004-11-14 23:57:20 UTC
The fact that it can be compiled but isn't yet in the tree is no blocker. 
If you think this blocks your gentoo life you should create an ebuild. We have more then enough real critical ebuilds allready. 
To repeat the policy again here is how we go over bugs: 
first the real bugs, errors, compile problems
then the keywording 
then if no other bugs are open : creating new ebuilds. 

Why very simple we are with few, and some off us use all the time they have to get  the current java tree working. That is our first priority. However, if people attach working ebuilds, and then we do make the effort to put them in the tree. 

this is no blocker, nor critical in fact it should be an enhancement over the existing 1.5 ebuild. 

greetings
Comment 5 Karl Trygve Kalleberg (RETIRED) gentoo-dev 2004-11-16 04:01:23 UTC
Check the quick analysis done by Dalibor Topic, the head Kaffe guy:
http://www.advogato.org/person/robilad/

The restrictions placed on the 5.0 release most definitely do not qualify as
open-source, I'm afraid, thus making this bug report moot.

Any of us developers who intend to patch Kaffe or any other open-sourced VM
are still not entirely in the clear:

"B. Residual Rights. You may use any information in intangible form that you remember after accessing the Technology, except when such use violates Sun's copyrights or patent rights."

I'd like to keep team exposure to the j2sdk sources as low as possible. Afaik, only Thomas is tainted in the current team.

I suggest interested parties update the 1.4.2 ebuild to work with the 5.0
release, and submit it as a new bug. Then we can persuade Thomas to test&commit.

Closing this as NEEDINFO, since we actually need an ebuild [we certainly don't have time to write one atm];)