Source: batik Version: 1.9-3 Priority: wishlist
batik pulls jython, and a whole load of related libraries, into the "key packages" set[1], which complicates transitions[2]. Please consider not building the Jython bindings, to drop this dependency. Upstream supports this, and the installed libbatik-java only suggests jython, as the bindings are entirely optional. The jython bindings don't seem to be used by any of the rdeps, but I didn't check very hard. Jython is generally not very widely used at all in Debian, which makes it reasonably easy to say this. As with most Java libraries, I expect any real users, if there are any, will be pulling the JARs from maven central, so won't care what we have built. Cheers, Chris. 1: https://udd.debian.org/cgi-bin/key_packages.yaml.cgi 2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828451#48 __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.