I've uploaded a new package to mentors that addresses this and #662198. I decided to add a Replaces/Breaks on libcvc3-2-jni, since the file /usr/lib/jni/libcvc3jni.so appears to be necessary for the binary package to function.
-Chris On Mon, Mar 5, 2012 at 11:08 AM, Christopher L Conway < christopherleecon...@gmail.com> wrote: > On Mon, Mar 5, 2012 at 3:08 AM, Ralf Treinen <trei...@free.fr> wrote: > >> Hello, >> >> On Sun, Mar 04, 2012 at 01:22:19PM -0500, Christopher L Conway wrote: >> > Not sure how to handle this. On the C++ side, the policy dictates a >> > libcvc3-X package with libcvc3.so.X and a libcvc3-X-dev package with >> > libcvc3.so -> libfoo.so.X. On the Java side, we don't have any >> headers to >> > install, so a libcvc3-X-jni-dev package seems like overkill just for >> a >> > libcvc3jni.so symlink. >> >> I have no idea about java packaging. Did you check what the debian Java >> policy says ? (not sure whether there is one, but at least there should >> exist such a policy :-) >> > > The Debian policy for Java on JNI packages ( > http://www.debian.org/doc/packaging-manuals/java-policy/x145.html) > provides no real guidance on this question akin to Debian Policy Sections > 8.1 and 8.5. > > -Chris > >
