Hi Nicolas, At the moment libneko is a private library in Debian, in the sense that it lives in /usr/lib/neko, and the neko and kaxe binaries use rpath to find it.
I have a request to "promote" libneko.so to be a real shared library
living in /usr/lib so that it is unnecessary to use rpath. (rpath gives
all kinds of problems if other packages start to link against libneko.)
I would like to do that, but there are a couple of problems which I
would need your help to overcome.
Problem 1: libneko does not have a SONAME. I have given it a SONAME in
the Debian package [1], but if I turn libneko into a public shared
library in Debian (and thus Ubuntu etc.), the SONAMEs have to be
carefully coordinated to not result in breakage on upgrades, security
uploads, and other packages depending upon it. So my question is
whether you are interested in adopting a consistent SONAME'ing scheme in
the files you distrubute?
Problem 2: The API in libneko uses very generic names. I have had a
suggestion that I should introduce some prefixing (like "neko_"), but
that would mean that your documentation would not match the libneko in
Debian, and I would really not like to do that. Do you have any
thoughts on that?
Cheers,
/JP
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
[1] I have attached the patch I use when building the libneko. The
rpath part would of course go away.
25-soname-rpath-strip.dpatch
Description: Binary data
