Hi Emmanuel, On Mon, Oct 19, 2015 at 12:15:35AM +0200, Emmanuel Bourg wrote: > libzmq-java/3.1.0-4 contains currently zmq.jar and its underlying native > library libjzmq.so. The Java Policy recommends splitting the native library > into a separate package libzmq-jni. Also ideally the .so should be installed > in a multi-arch path.
I think we already discussed that during the ITP phase: As both the native library and the zmq.jar are really small (28k and 48k), I don't think splitting the package up would be useful. Additionally, the java policy reads: "There may be situations, such as with very small packages, where it is better to bundle the Java code and the native code together into a single package. Such packages should be architecture-specific and follow the usual libXXX[version]-java naming convention." So, please convince me with some real advantages of splitting the package. Best regards, Jan
