There's no jar file called derby, although it should be there, as derby(javadb) are now oficially included in java 1.6 Reproducible: Always Steps to Reproduce: Just emerge the package with this flags : dev-java/sun-jdk-1.6.0-r1 USE="X alsa -doc -examples -jce -nsplugin" Actual Results: There's no javadb or derby .jar file Expected Results: It's supposed to have one dev-java/sun-jdk-1.6.0-r1 USE="X alsa -doc -examples -jce -nsplugin" Portage 2.1.2_rc4-r8 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.5-r0, 2.6.18-suspend2 i686) ================================================================= System uname: 2.6.18-suspend2 i686 Intel(R) Celeron(R) M processor 1.50GHz Gentoo Base System version 1.12.8 Last Sync: Thu, 11 Jan 2007 14:50:01 +0000 dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.3.6, 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/confcache: 0.4.2-r1 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.19 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=pentium-m -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.ludost.net/gentoo ftp://mirrors.ludost.net/gentoo/ http://distfiles.gentoo.org" LC_ALL="bg_BG" LINGUAS="bg en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/layman/sunrise /usr/portage/local/layman/stuart-desktop" SYNC="rsync://mirrors.ludost.net/gentoo-portage" USE="X acpi alsa berkdb bitmap-fonts cli cracklib crypt cups dbus dlloader dri fortran gdbm gif glitz gpm hal iconv ipv6 isdnlog jpeg kde kdexdeltas libg++ mmx ncurses nls nptl nptlonly opengl pam pcre perl ppds pppd python readline reflection session spl sse sse2 ssl tcpd truetype-fonts type1-fonts udev unicode x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="mouse keyboard synaptics" KERNEL="linux" LINGUAS="bg en" USERLAND="GNU" VIDEO_CARDS="vesa fbdev i810" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
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
