[Charles Fry] > According to the current java policy, section 2.4: > > "Java libraries packages must be named libXXX[version]-java (without > the brackets), where the version part is optional and should only > contain the necessary part. [...] > In other words, if distributing the jar 'svn-javahl.jar', the package > should be named 'libsvn-javahl-java'. Though I can't help but wondering > about the value of the javahl part of the package name. Yes, I wonder about that too. The jar file really is named svn-javahl, for historical reasons: there was once a second effort (now dead, I believe) to produce java bindings which were not "high-level". There is also an independent project out there, not affiliated with the Subversion project and not in Debian, which reimplements svn client functionality purely in java. I don't know the name of their jar file. So ... I'm CCing this to the debian-java list with a question: is it reasonable to name a package 'libsvn-java' if the jar file it ships is named svn-javahl.jar? I really don't like 'libsvn-javahl-java' as a name (reminds me of 'python-pyvorbis'), but if policy requires it, we'll use it. Thanks, Peter
Attachment:
signature.asc
Description: Digital signature