Hi Jérôme,
Le 24/10/2023 à 15:18, Jérôme Charaoui a écrit :
I've prepared the jruby-jzlib package, but I'm uncertain about the
relationship it should have with jzlib.
Since the module itself is still using the same "com.jcraft" namespace,
I'm thinking of using a Conflicts: and Provides: on libjzlib-java.
No that's not necessary, because the libjzlib-java and
libjruby-jzlib-java packages do not conflict at the filesystem level.
The Conflicts field doesn't cover classpath conflicts.
You can check out the package here:
https://salsa.debian.org/lavamind/jruby-jzlib
I got a quick look at the jzlib fork [1] and there are very few changes
compared to the original project, it just adds a JPMS auto module name.
We could simply patch our existing jzlib package instead of introducing
a new one. On the jruby side, that would mean patching the Maven
coordinates of jzlib (org.jruby:jzlib -> com.jcraft:jzlib).
Emmanuel Bourg
[1] https://github.com/jruby/jzlib
