Hi, just some quick comments.
> http://mjj29.matthew.ath.cx/debian-upload/libmatthew-java/ Your package contains about 40 source files and builds five different binary packages. How do you justify this? Why not simply roll the classes into the main package? Since your classes appear to solve problems that should have existing solutions (such as printing DOM trees), couldn't you just use one of the standard solutions that are already packaged? > Package: libunix-java Please choose a less ambiguous name. > Depends: ... java-gcj-compat | java-runtime | java-compiler ... This dependency looks strange, java-compiler should probably be removed. > Description: Extra IO library for Java > This library provides classes to pipe a stream through an external > program, print DOM trees and split an output stream so that it also goes > to a file. These tasks seem very disjoint for a library. > Package: libmatthew-debug-java > This library provides a comprehensive debug and logging suite for Java. If we are talking about the file Debug.java (600 lines), that's a bit exaggerated, don't you think? Your debian/rules seems to depend on very specific versions of java-gcj-compat-dev, that should be fixed. Regards, Marcus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
