eclass doesnot call regso upon instalation which causes the resulting env files not to have a LIBRARY_PATH definition. Reproducible: Always Steps to Reproduce: 1.emerge any java-gnome component 2. 3. Actual Results: env file does not have a LIBRARY_PATH definition. Expected Results: env file should have a proper LIBRARY_PATH definition. /usr/share/glib-java-0.2/package.env contents DESCRIPTION="Java bindings for glib" GENERATION="2" CLASSPATH="/usr/share/glib-java-0.2/lib/glib0.2.jar" VM=">=virtual/jre-1.4" TARGET="1.4" SOURCE="1.4" JAVA_SOURCES="/usr/share/glib-java-0.2/sources//glib-java-src.zip" MERGE_VM="sun-jdk-1.6"
Is this a big problem as java should find them in /usr/lib where they get installed? The next version bump will not use the eclasses any way as it will be just one ebuild so we should just make sure that it does the things properly.
(In reply to comment #1) > Is this a big problem as java should find them in /usr/lib where they get Could be a problem - bug 125563
4.0.3 is only one package and does not use java-gnome.eclass any more so this bug can be marked as fixed.