Marcus Better wrote: > Most of the Debian library packaging guide [1] applies to Java libraries > too. It seems to me that this problem has been ignored for Java libs just > because Java doesn't automatically force us to deal with it, like SONAMEs > do to some extent. > I'm not sure if our ideas are really opposed: I'm talking about detecting ABI problems automatically within the distribution through rebuilding the transitive chain of reverse dependencies of an updated package (i.e. detecting FTBFS problems caused by the update) and running their tests to potentially detect breaking API changes automatically.
You seem to be arguing for packagers to be careful about documented ABI/API changes in the code and to check for them manually, if necessary. I believe those approaches are complementary. cheers, dalibor topic _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
