libpri1, libpri1.2, SONAMES etc.

[Tzafrir Cohen]

On Thu, Jul 26, 2007 at 09:21:03PM +0300, Faidon Liambotis wrote:
> Mark Purcell wrote:
> > On Sun, 22 Jul 2007, Faidon Liambotis wrote:
> >> PLEASE DO NOT UPLOAD A NEW libpri TO Debian BEFORE DISCUSSING THIS.
> >> It will only make the mess worse.
> 
> > Have we arrived at a concensus?
> No we haven't yet, I think.
> 
> I didn't have the time to test whether libpri 1.4 works with Asterisk
> 1.2 yet, unfortunately.
> 
> > 1.4.x soname:  libpri.so.1.0    packagenames: libpri1.0 libpri-dev
> > 1.2.x sonames: libpri.so.1.0 libpri.so.1.0   packagenames: libpri1.2 libpri1.2-dev
> > 
> > libpri1.0 to conflict with libpri1.2
> That's certainly wrong.
> 
> There are two scenarios:
> a) They're ABI-incompatible: they should have a different SONAME (e.g.
> libpri.so.1.4/libpri.so.1.2) therefore a different package name
> (libpri1.4/libpri1.2) and they shouldn't *AT ANY CASE* conflict each other.
> 
> b) They are ABI-compatible: we should drop libpri 1.2, pick one SONAME
> for libpri 1.4 (probably libpri.so.1.2, I think libpri 1.0 had a
> different ABI) and the according package name (libpri1.2).
> Also, use "dh_makeshlibs -V libpri1.2 (>= 1.4)" because the
> compatibility is going to be one-way (Asterisk 1.4 isn't able to use
> libpri 1.2, obviously)
> 
> Based on the header diff, I believe that they are compatible, so (b)
> will apply.
> However, they may have a changed the internal behavior in a way that
> Asterisk 1.2 doesn't expect, in which case we should go for (a).

Keving Flemming believes otherwise:
from #asterisk-dev a while ago:

<tzafrir_laptop> 
BTW: what exactly is the compatibility status between
libpri in asterisk 1.0, 1.2 and 1.4?
the soname is the same, so the directory pretends to be compatible
This is just now being discussed at the debian
packagers list: do we need to change the soname and have separate
packages for 1.2 and 1.4, and can we just keep the single package of 1.4

<kpfleming> 
unfortunately it is not compatible, and we do not do a good
job of naming things properly to deal with that
there are API differences include differently-sized
structures between the version

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir