-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-08-12 10:26, Jan-Pascal van Best wrote: > On Thu, August 12, 2010 09:54, Niels Thykier wrote: >> I just realised that a likely side effect of implementing this idea is >> that we can no longer allow programs to ship jar files in >> /usr/share/java and instead these must be moved to a separate library >> package (or moved to /usr/share/$pkg). > > Why would that be? C libraries are installed in /usr/lib/ with a > comparable naming scheme. > > Jan-Pascal > > > >
The reason is that if the library is in /usr/share/java it would be considered a public library (just as C libraries in /usr/lib) and therefore it would need to be in a library package to declare its ABI version[1]. You cannot do that with a program package (unless you start adding ABI versions to the program package name which would probably be "less than optimal solution"). ~Niels [1] (Quoting the original mail on this): - Library packages must include the ABI version in the package name, so the source package will be called foo0, the binary package will be called libfoo0-java etc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkxjvjEACgkQVCqoiq1YlqymowCg5uvlNJvcXOAtA7zb/nVbcYoe o80AoJc3XED/KhZ8upXXq7A0yvT7VYg0 =TlIY -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c63be31.9080...@thykier.net
