The jdbc3-postgresql ebuild fails on systems with sun-jdk installed. The reason is that the sun-jdk can only handle -target 1.5 and denies service to lower platform settings as the ebuild expects. In order to fix this problem, go to the postgresql website and read which target by which jdbc driver is supportet. in my case, i changed the ebuild to the following: # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/dev-java/jdbc3-postgresql/jdbc3-postgresql-8.1_p404-r1.ebuild,v 1.1 2006/07/01 15:31:11 nichoj Exp $ inherit java-ant-2 java-pkg-2 MY_PN="postgresql-jdbc" MY_PV="${PV/_p/-}" MY_P="${MY_PN}-${MY_PV}.src" DESCRIPTION="JDBC Driver for PostgreSQL" SRC_URI="http://jdbc.postgresql.org/download/${MY_P}.tar.gz" HOMEPAGE="http://jdbc.postgresql.org/" LICENSE="POSTGRESQL" SLOT="0" KEYWORDS="~x86 ~ppc ~sparc ~amd64" IUSE="doc examples source" DEPEND=">=virtual/jdk-1.5 >=dev-java/ant-core-1.6 source? ( app-arch/zip )" RDEPEND=">=virtual/jre-1.5" # Apparently this has 1.5 specific features, which will need to handled # somehow with use flags, and may need to patch build.xml to make sure the # right -source / -target are used JAVA_PKG_NV_DEPEND="=virtual/jdk-1.5*" S="${WORKDIR}/${MY_P}" # There are 1.5 features, which jikes doesn't like java-pkg_filter-compiler jikes src_compile() { eant jar $(use_doc publicapi) } src_install() { java-pkg_newjar jars/postgresql.jar ${PN}.jar use doc && java-pkg_dohtml -r ${S}/build/publicapi/* if use examples; then dodir /usr/share/doc/${PF}/examples cp -r ${S}/example/* ${D}/usr/share/doc/${PF}/examples java-pkg_dojar jars/postgresql-examples.jar fi use source && java-pkg_dosrc ${S}/org } After this fix ( change 1.4 to 1.5 ), enter "ebuild /usr/portage/dev-java/jdbc3-postgresql/jdbc3-postgresql-8.1_p404-r1.ebuild digest" and emerge your jdbc3 driver. Stay tuned, the next sync is in the near future. Please fix it permanently. Best regards, Doreen.
Created attachment 90635 [details, diff] This diff fixes the problem for users who don`t want to install blackdown java
Comment on attachment 90635 [details, diff] This diff fixes the problem for users who don`t want to install blackdown java >--- /usr/portage/dev-java/jdbc3-postgresql/jdbc3-postgresql-8.1_p404-r1.ebuild 2006-07-01 20:30:19.000000000 +0200 >+++ jdbc3-postgresql-8.1_p404-r1.ebuild 2006-07-01 21:14:23.000000000 +0200 >@@ -17,15 +17,15 @@ > KEYWORDS="~x86 ~ppc ~sparc ~amd64" > IUSE="doc examples source" > >-DEPEND=">=virtual/jdk-1.4 >+DEPEND=">=virtual/jdk-1.5 > >=dev-java/ant-core-1.6 > source? ( app-arch/zip )" >-RDEPEND=">=virtual/jre-1.4" >+RDEPEND=">=virtual/jre-1.5" > > # Apparently this has 1.5 specific features, which will need to handled > # somehow with use flags, and may need to patch build.xml to make sure the > # right -source / -target are used >-JAVA_PKG_NV_DEPEND="=virtual/jdk-1.4*" >+JAVA_PKG_NV_DEPEND="=virtual/jdk-1.5*" > > S="${WORKDIR}/${MY_P}" >
Created attachment 90636 [details, diff] This fixes the problem for users who don`t want to install blackdown java
For future reference, it really is only necessary to attach the patch, no need to post comments with it inline.
Could anybody update ebuild in portage?
This "bug" is closed as the new java-policy works fine on all platforms. Blackdown and Sun Java coexist bravely on the harddisk and the gentoo-specific config tools are working fine. No need to worry about. Everything is fine, nothing is ruined.
The "BUG" is closed. The Gentoo specific java policy works fine and there is no need to worry about it any more. The following VMs are available for generation-2: 1) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] *) Sun JDK 1.5.0.08 [sun-jdk-1.5]
