Le vendredi 12 novembre 2010 à 09:51 -0500, Scott Howard a écrit :
> I would to revisit this bug. I agree with the debian policy decision
> to keep compiled binaries in /usr/lib/jni/, but I'm getting frequent
> bug reports and emails form users of a library I maintain telling me
> that I installed the library to the wrong location [1-8, and personal
> correspondence]. I know we can't change the binaries, but can we
> somehow export this simple variable [9] in a wrapper so that all
> systems (that install sun-java) know to look in /usr/lib/jni? I think
> that would be a simple solution that will satisfy users so that they
> don't think our libraries are all broken.
>[9] LD_LIBRARY_PATH="/usr/lib/jni${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"On Fri, Nov 12, 2010 at 11:57 AM, Sylvestre Ledru <sylves...@debian.org> wrote: > I agree with you we should do that. > I had a (too) quick look on this and doing some modifications > in /etc/java-6-sun/* might fix this bug. That would work too, I'm not too familiar with how the sun package is put together with the properties files in /etc, but the java.library.path property is what should be appended (or set). a properties file that looks something like: # Tells java to look for JNI libraries in the Debian policy location java.library.path=/usr/lib/jni I don't know if we would need to do some substr magic to append the path, or if that is typically an empty variable to begin with. I couldn't find documentation saying whether or not it should be appended or if it is ok to set to a single directory. I also don't know if a user setting LD_LIBRARY_PATH on their own overwrites our java.library.path -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikgtn1wsf0e7sce_nsf_rboada=mc-r7t_3v...@mail.gmail.com
