libpri1, libpri1.2, SONAMES etc.

[Kilian Krause]

Tzafrir,

On Sun, Jul 22, 2007 at 09:47:53AM +0300, Faidon Liambotis wrote:
> Faidon Liambotis wrote:
> > libpri 1.4:
> >    SONAME: 1.4
> >    -dev package name: libpri1.4-dev
> >      i.e. contains: /usr/lib/libpri.1.4
> > libpri 1.2:
> >    package name: libpri1.2
> >    -dev package name: libpri1.2-dev
> >    SONAME: 1.2
> >      i.e. contains: /usr/lib/libpri.1.2
> I began implementing this almost according to plan. The following 
> changes/problems occured:
> a) libpri.so.1 is useless, therefore dropped
> b) the sources are libpri and libpri1.2. The second one is providing 
> libpri1.2-dev, but what about the first one? Should it provide 
> libpri1.4-dev? What is going to be with libpri 1.6?

is going to be libpri1.6-dev. We'll just run it through NEW as upstream
doesn't hold the API/ABI stability. Btw. as a side note: I've looked out
for a long time for a script that can verify both API and ABI during
compile time. That means that you initially commit a fingerprint to the
SVN and if that's broken, the package will not be rolled out. Thus, the
package needs to be updated and moved to a new soname. Until now I
haven't found it, but I'm willing to help testing it and getting it into
debhelper.


> I haven't commited anything wrt to the SONAME change since it's still in 
> flux and there isn't a consensus yet (and branches in SVN suck).

Consensus is that we'll just spin each 1.x series in its own SONAME
space. If we can reduce that with a check script during compile time, we
should do that. Yet until such a script exists, we'll need to manually
look after it.


> But that's not why I'm mailing again.
> 
> I just did a quick diff between libpri1.2/trunk/libpri.h and 
> libpri/trunk/libpri.h and the changes seem to be compatible.
> 
> Has anyone tried running Asterisk 1.2 with libpri 1.4?

Tzafrir had a short look. And at that time there was no bristuff.


> I also diffed libpri1.2 + bristuff and libpri1.4 + bristuff and they are 
>   identical, besides the Digium changes.
> 
> If that's the case, and we are going forward with bristuffed Asterisk 
> 1.4, we should drop libpri1.2 completely.

If you do reckon that it will work, even better. Go ahead and drop it!
;)


> Fixing the SONAME in 1.4 should be done IMHO and we could just have 
> libpri1.4 Provides libpri1.2. Old packages should work, while new 
> packages (which may use pri_keypad_facility, the new function) will 
> depend on libpri1.4.

Sounds sensible.


> Can someone test it?

You? Tzafrir?

-- 
Best regards,
Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20070722/a52951c5/attachment-0001.pgp