Summary: | Blackdown-jre ebuild no longer working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Todd Geders <geders> |
Component: | New packages | Assignee: | Karl Trygve Kalleberg (RETIRED) <karltk> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | kevin |
Priority: | Highest | ||
Version: | 1.2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Todd Geders
2002-09-05 12:54:13 UTC
Yes, I have found the same problem myself. Portage downloads index.html and j2re-1.3.1-FCS-linux-* from whatever mirror your use, then fails to unpack the tgbz2, and then installs an empty /opt/blackdown-jre. The "fix" is to fallback to the /usr/portage/dev-java/blackdown-jre that is distributed on the 1.2 ISO. Whoever broke this should be slapped around with a live trout. (whatever the environmentalists might say) The worst of it, is that that portage-current shows blackdown-jre-1.3.1-r7... The same as is distributed with 1.2. Hope someone with CVS commit falls back to the stable version. Now it installs fine, but the mozilla plugin symbolic link seems to not be
generated properly on my machine. Last thing the ebuild does is:
>>> /usr/lib/mozilla/plugins/javaplugin_oji.so ->
/opt/blackdown-jre-1.3.1/plugin//mozilla/javaplugin_oji.so
However between the /'s in ...plugin//mozilla... it should place ${PLATFORM},
but mine is being generate blank. Since this is a fresh 1.2 install, anyone
trying to install 1.2 will still get a broken java-vm in Mozilla.
Whooops. Major oversight. |