Manoj Srivastava wrote: > Should policy explicitly deprecate this methodology? I am > inclined to think so, but I'm willing to be taught the error of my > ways.
We already had this discussion on Debian-Java last year but did not find a solution there. I also have a package that just copies a jar archive to the .deb (gnujsp) because there could be some incompatibilities or even bugs (the early versions of jikes produced buggy code for gnujsp). I then decided to just copy the .jar so I distribute the same classes as the upstream authors and I am sure that upstream bugs are really upstream bugs and not my fault. I got a lot of bug reports about gnujsp in private mail that could all be solved by switching from kaffe to Sun's oder IBM's JDK - I don't want to think about the number of incompatibilies or bugs we could introduce by compiling your classes with kaffe/classpath (and Debian would surely prefer to use free tools to compile packages). -- Stefan Gybas
