Summary: | dev-java/sun-jdk-1.6.0-r1 - Javadb (derby) not included | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Boyan Ivanov <tindor> |
Component: | New packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | p.gentoo, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6562662 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Boyan Ivanov
2007-01-11 16:37:38 UTC
derby is located in db subdir after unpacking the distfile, we are not installing it though yet... should we make it optional or mandatory? (or separate package?) there is some stuff we shouldn't install for sure (frameworks subdir serves as an example and contains for example executable .bat files..., demo) and it contains extra licenses - apache 2.0 and sun's early access which is probably there since the early snapshots and they forgot to remove it from final version? that should be probably reported as issue on jdk-distros. I think the best would be to package derby from sources (http://db.apache.org/derby/) as separated package, and maybe USE flag in sun-jdk could create symlink to that, to provide layout some unfortunate stuff might expect, for the end user. Should also save us from the situation that some stuff starts depending on derby, we lock it to jdk 1.6 and then ibm releases its 1.6 without bundled derby... <brain switch="on"> vi /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0-r1.ebuild src_install() { - local dirs="bin include jre lib man" + local dirs="bin include jre lib man db" ebuild /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0-r1.ebuild digest <brain switch="off"> (In reply to comment #2) > I think the best would be to package derby from sources > (http://db.apache.org/derby/) as separated package, and maybe USE flag in > sun-jdk could create symlink to that, to provide layout some unfortunate stuff > might expect, for the end user. Should also save us from the situation that > some stuff starts depending on derby, we lock it to jdk 1.6 and then ibm > releases its 1.6 without bundled derby... > I think we should use flag it as it's optional. http://download.java.net/dlj/jdk6/README.html#redistribution Yeah let's USEflag it for those who want it, no need to delay more until we have time to package derby from source... Could go with 1.6.0.01 if they release it under DLJ soon (bug 172854). Hm, seems that Sun decided to stop bundling it with the JDK. See the New features section in http://download.java.net/jdk6/6u2/promoted/b02/changes/jdk6u2-b02.html and especially http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6530097 . I've confirmed that the db dir is gone in 6u2b02 while it was there in b01. In this case I doubt it makes much sense to install the bundle now, just to remove it in June when 6u2 should be released. Should probably focus on separate ebuild for derby instead. There's already some skeleton in overlay. The db dir is gone from final (non-DLJ) 6u2. Unless it magically appears in DLJ version, it's CANTFIX here (and new bug to package derby from source). Fixed in sun-jdk-1.6.0.14 |