Sort of strange, and I can't place theese. "clean" stage3 + emerge -v portage; emerge -vu python, python-updater (means I got X, tcl and so on) from "emerge -kvp --debug kde" : ldap encode cups oggvorbis opengl ssl pam ldap motif encode cups oggvorbis opengl ssl pam java /usr/sbin/ebuild.sh: line 1: java-config: command not found ldap motif encode cups oggvorbis opengl ssl pam java /usr/sbin/ebuild.sh: line 1: java-config: command not found and true. java-config isn't installed, so why does ebuild.sh call for it?
Spider i think this is a portage bug, instead of a java-config bug.
it's a kde bug ... many of their ebuilds put code into global scope (and in this case, java-config is called in global scope) this, btw, is not a good thing :P
Well, thats suspectible, even if I had expected that the new portage would whine about "java-config in global scope" and churn out the ebuild in question.
If this is kde's fault, and it's known, can someone explain it to me rather than assume I know?
sure. here for example, kdebindings : DEPEND="=kde-base/kdebase-${PV}* =x11-libs/gtk+-1.2* dev-lang/perl python? ( dev-lang/python ) java? ( virtual/jdk ) =dev-libs/glib-1.2* ~kde-base/kdenetwork-${PV} mozilla? ( net-www/mozilla )" use python || myconf="$myconf --without-python" use java && myconf="$myconf --with-java=`java-config --jdk-home`" || myconf="$myconf --without-java" See that "--with-java" .. .line? At this point in time DEPEND isn't satisfied, its still doing deptracking, which means that java-config isn't installed.
Gotcha - so adding a bash test for the existance of java-config prior to rnning it would be a step in the right direction?
move those statements inside src_configure instead by doing "bash -x foobuild.ebuild" -no- code should be executed, not even to evaluate variables, so the correct path is to have the flags inside something like src_compile() { use java && myconf=`java-config --` kde_src_compile() } or akin.
this is fixed in the latest kde ebuilds.
