At DebConf10 the Java Team considered look at making a similar
infrastructure for Java libraries as we currently have for C/C++
libraries. While not all things can be transferred (e.g. we cannot
binNMU arch:all packages and no -dev packages), we can still gain a lot
from automated ABI/API breakage detection and well defined transitions.
As it is now, we manually create a libXY-java package if we suspect
that the new version of libX-java is not backwards compatible.
First of all I was hoping that you might have some "Do" or "Don't"
pointers from when dpkg added support for these things. Secondly, there
might be some code or infrastructure that could be shared.
Particularly I am interested in how you handle mapping
filenames/SONAMES to a package (especially in cases like libc6, where
there more than one lib in the package).
We also have cases where two packages provide the same library and it
would be optimal for us to end up with libX-java | libY-java in the
depends, but I have a feeling that is not entirely trivial to support
(in a sane way).
I intend to have all the tools to support this in the javahelper
package. I am not too sure that we can recycle the existing formats
(maybe the shlibs format with s/SONAME/filename/) as we have to check
for things like classes, return-types, inheritance and method
overloading as well. But feel free to correct me if symbols files
already have support for this.
Thanks in advance,
PS: Please keep me in CC.
 Such being able to tell if reverse dependencies have been rebuilt
against the new version of a library or not.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
To UNSUBSCRIBE, email to debian-dpkg-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com