On 28/08/15 18:00, Simon McVittie wrote:
On 28/08/15 14:45, Eugen Dedu wrote:
On 27/08/15 00:46, Simon McVittie wrote:
On Wed, 05 Aug 2015 at 17:53:15 +0200, Eugen Dedu wrote:
knowing that ptlib changes soname with *each* release
...
As the two versions 2.10.10 and .11 are API/ABI compatible
Please educate your upstream about what SONAMEs mean?
You are right to follow upstream's SONAME scheme rather than inventing
Debian-specific SONAMEs. However, the SONAME should normally only change
if the new version's ABI is incompatible with the old; this is something
that upstream developers of libraries are expected to get right.
See: <https://www.debian.org/doc/debian-policy/ch-sharedlibs.html>
I know this is not "classic". We have discussed this with upstream.
Upstream changes often the API/ABI, and he has not the time to maintain
older versions. ptlib/opal have 700 klines of code, and targets also
windows, macos, various customers etc. Really, there is nothing we can do.
this is only
a matter of changing .10 to .11 in debian/control for those packages.
I thought for a moment that you meant the reverse-dependencies
hard-coded the ptlib version number, either directly or by
build-depending on a -dev package with the version in.
Thankfully, they do not: the -dev package is libptlib-dev, and simply
rebuilding the reverse dependencies (which the release team will
schedule to be done automatically) will result in picking up the new ptlib.
You are right, sorry.
I have just committed the changes in debian/ to allow building ptlib
2.10.11, they are at
http://anonscm.debian.org/viewvc/pkg-voip/ptlib/branches/ptlib2.10-luyten.
I have also built the package, the generated files are at
http://eugen.dedu.free.fr/ek-debian.
Thanks, I'll try to find time to check that.
Ok.
--
Eugen
