Bug#220237: libfop-java is a target of deborphan

[Stefan Gybas]

James Troup wrote:

> Sorry but that's just stupid.  It's trivial to work around the problem
> mentioned and a whole bunch of packages violate this "serious" policy
> violation and have done for years without problems.

I have no problem with the script and the JAR being in the same package. 
The package should just not be in the libs section and named like a 
library (since it's obviously not just a library but a complete 
application).

 > Ola is right to not want to create a package with nothing but a <20 
line script.

I have never suggested to create a separate package. In fact, I'm 
against creating a separate package. I'm also against the m

 > (And if it is a script rather than a binary, you can probably bypass the
> policy fascists because it won't use the shared library)

Strictly speaking, Java libraries in JARs are not even "shared library" 
in Policy's definition.

The easilest solution would be to rename the package and put it in a 
different section. Don't you agree? If you think that's not necessary, 
feel free to close the bug report.

Stefan