On 10/28/2010 06:48 AM, Ximin Luo wrote: > Package: libbsf-java > Version: 1:2.4.0-4 > Severity: grave > Tags: patch > Justification: renders package unusable > > The currently-distributed bsf.jar does not contain the adapter classes (in > org/apache/bsf/engines) for most of the optional languages, except XSLT. This > renders the package mostly useless and is contradictory to the description, > which implies that (e.g.) installing rhino will enable JavaScript support. > > This is because the build script tests for rhino, and will exclude the engine > for it, if it's not detected. In other words, to build a proper package that's > useful for the maximum number of people, you need to install all the optional > libs at *build time* and make them available to the build script. > > I've attached a patch (for debian/patches) which automatically looks for the > optional jars in their default Debian locations (/usr/share/java) and will > include BSF's adapter classes if detected. I suggest also making those > packages > strict Build-Depends so as to not accidentally make this mistake in the > future.
Hello Ximin, I've applied the patch and committed the update to the packaging repo. I wanted to ask the debian-java team if there were any opinions about whether or not to go ahead and declare explicit build-deps on the language JARs that are available in Debian. It seems useful to have as much support as possible compiled into the library. I'm not sure I agree with the severity - the current package isn't completely unusable, is it? (Your bug report says "mostly useless.") Would severity important be more appropriate? Cheers, tony
signature.asc
Description: OpenPGP digital signature