[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Symbols/shlibs files for Java



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi

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[1].
  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,
~Niels

PS: Please keep me in CC.

[1] 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/

iQIcBAEBCAAGBQJN3N4fAAoJEAVLu599gGRC4NAP/AjdOPHYmZWC94ILdezu7Mmy
Ubo8gc5uTilUtJVyArpGyfM/7RBGLKaY23DIUkjlYk2JwZ0Eisvsz1vA+/KJbUMw
LTO9iGfRBhi71v0uWyrBvmDusmaU5RbicwugIbNbJ0eysDvx5akjtlJIvwI/whsD
EYMJTF6bk+p6ZhRCbCZMdnctr4cIc8fT3nB8HWCVkpIYRwvGNONXSXYmmj2tmjPX
jF7biJqMxaPszwe2xHqhhTmY3OEB9kTws9hMJ40wPBcBMKlgW6go+1X1uBHGajHc
AOXjBjIUoUM10HoIlbdHEr6EbZhFHQQsCZFo2/uuKHzjYxyYnu+NJ50pl1LwzbZz
/uyXuLaYBzjfTNY8dYsmKFhrnSgo/K7cgMuWcvbGYgxTT0HfUlK4XQ6F19NJzaYi
LZCCMcs2Stjq5eGoqHkB+igayVy9cxE0JQLyCbKkgGxDm7Yx4gsmOKxZW36WzYTt
LGwIrwiUJu8hCKDTVzo+dYL6+XX8jH3XTSWqHvPYo+4aIJ1teXvZcodGfvk0bWOj
cvsz5V1TkV2jgZA+zLzAr6mSPEsaPdbwnQOfZ2ZOx8iJghzRLWbNpxXgU3rmtdPy
9JBVwmS6MMIEWlk6d9UwJ+urbz0gnK9H3sTb9ea25blCDBLGjK+7EGfjkW1+Yju2
3sSuBwPz8GNqSU6rnafs
=0Mvx
-----END PGP SIGNATURE-----


Reply to: