On Thu, 5 May 2011 16:47:06 +0200 (CEST), Yamaban
What's the 'offical' take on /usr/share/java* wrt binary libs/plugins ?
IMO if its java bytecode it's OK but not for binaries compiled for a certain platform. Those belong in a directory below /lib or /lib64.
In the tenor you've given, I'd say the use of LD_LIBRARY_PATH in the start-script would be the best solution in this case.
It won't help! If the application has the path to the library hard coded no trick besides a symlink will help you to load it from somewhere else. LD_LIBRARY_PATH will only help when the application requests the library by name. Example: gcc -shared -o libfoo.so -fPIC foo.o -L$(JAVA_HOME)/lib/jre/amd64 \ -ljawt In that case libfoo.so will have libjawt.so recorded in its DT_NEEDED field (as you can see by doing 'objdump -p' on the binary). The above plugin will only work if either the non-standard path to the AWT lib is put into /etc/ld.so.conf or if you set LD_LIBRARY_PATH. BTW, LD_LIBRARY_PATH is ignored for binaries with effective uid root as that would otherwise open a huge security hole. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org