Re: SONAME in C++ libraries

[Andreas Fester <Andreas.Fester@gmx.de>]

Shachar Shemesh wrote:
> Hi all,
> 
> I'm working on packaging xparam (http://xparam.sf.net). It's a C++
> library for object serialization.
> 
> The problem is that upstream does not belive in SONAME versioning for
> C++ libraries. He claims that he has no choice but to break interface
> with each and every release. As a result, he is giving all libraries a
> "1.0.0" version.

See
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html

especially

http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameoftenchange

> I'm thinking of changing that to "0.0.0", so that the nature of the
> incompatibility is clear. The question is whether such a change from
> upstream is considered legitimate?

If upstream is unwilling to change the SONAME each time the binary
compatibility breaks, then IMHO the only choice is that you do it
yourself for the Debian package. Otherwise trouble begins when other
packages within the Debian archive start linking against your library.
See also http://www.trolltech.com/developer/faqs/index.html?catid=&id=362
for what breaks binary compatibility of C++ libraries.

Best Regards,

	Andreas

-- 
Andreas Fester
mailto:andreas@littletux.net
WWW: http://www.littletux.net
ICQ: 326674288