Bug#802276: libzmq-java: Move the native library to libzmq-jni

[Emmanuel Bourg]

Le 21/10/2015 16:14, Jan Niehusmann a écrit :

> So, please convince me with some real advantages of splitting the
> package.

Hi Jan,

The policy was written before the multiarch move and should probably be
revised. Merging the -java and -jni parts doesn't allow the
co-installation of the library for different architectures on the same
system. And running 32 bits VMs on 64 bits systems is quite common.

Emmanuel Bourg

Bug#802276: libzmq-java: Move the native library to libzmq-jni

[Jan Niehusmann]

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

Bug#802276: libzmq-java: Move the native library to libzmq-jni

[Emmanuel Bourg]

Package: libzmq-java
Version: 3.1.0-4
Severity: normal

Dear Maintainer,

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.

Emmanuel Bourg