Re: SONAME in C++ libraries

2005-10-13 Thread Steve Langasek
On Thu, Oct 13, 2005 at 01:57:27PM +0200, Andreas Fester wrote: > Shachar Shemesh wrote: > [...] > > What I thought was to use "0" as SO version, which is a standard way to > > state that the interface is not guarenteed to remain stable. I'll also > I did not know about this. Do you have a pointer

Re: SONAME in C++ libraries

2005-10-13 Thread Andreas Fester
Shachar Shemesh wrote: [...] > What I thought was to use "0" as SO version, which is a standard way to > state that the interface is not guarenteed to remain stable. I'll also I did not know about this. Do you have a pointer to the appropriate section in the Debian policy or some other document?

Re: SONAME in C++ libraries

2005-10-13 Thread Josselin Mouette
Le jeudi 13 octobre 2005 à 12:51 +0200, Shachar Shemesh a écrit : > What I thought was to use "0" as SO version, which is a standard way to > state that the interface is not guarenteed to remain stable. I'll also > add a comment to readme.Debian to the effect that, when linking against > the librar

Re: SONAME in C++ libraries

2005-10-13 Thread Guus Sliepen
On Thu, Oct 13, 2005 at 12:51:01PM +0200, Shachar Shemesh wrote: > Andreas Fester wrote: > > >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 o

Re: SONAME in C++ libraries

2005-10-13 Thread Shachar Shemesh
Andreas Fester wrote: >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.

Re: SONAME in C++ libraries

2005-10-13 Thread Andreas Fester
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

SONAME in C++ libraries

2005-10-13 Thread Shachar Shemesh
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