Re: how to check for binary compability?

2009-05-27 Thread Jonas Meurer
Hey, On 27/05/2009 Russ Allbery wrote: > Jonas Meurer writes: > > so only one question remains for me: do I need to bump the soname or at > > least provide a symbols file for added library symbols? or can I simply > > ignore them as well? > > You should not bump the SONAME. You should bump the

Re: how to check for binary compability?

2009-05-27 Thread Russ Allbery
Jonas Meurer writes: > so only one question remains for me: do I need to bump the soname or at > least provide a symbols file for added library symbols? or can I simply > ignore them as well? You should not bump the SONAME. You should bump the shlibs dependency (as generated by dh_makeshlibs if

Re: how to check for binary compability?

2009-05-27 Thread Jonas Meurer
Hey Jan, thanks a lot for the detailed analysis :-) On 26/05/2009 Jan C. Nordholz wrote: > >>> [_ZN8DwStringixEj] > > that symbol is defined in mimelib/mimelib/string.h as > > ] inline char& DwString::operator [] (size_t aPos) > > It is pulled in by mimelib/param.cpp because of > > ] void DwP

Re: how to check for binary compability?

2009-05-26 Thread Jan C. Nordholz
Hi Jonas, >>> [_ZN8DwStringixEj] that symbol is defined in mimelib/mimelib/string.h as ] inline char& DwString::operator [] (size_t aPos) It is pulled in by mimelib/param.cpp because of ] void DwParameter::Parse() ] { ] [...] ] if (len > 2 && mValue[0] == '\'' && mValue[len-1] == '\'')

Re: how to check for binary compability?

2009-05-26 Thread Jonas Meurer
Hello, On 26/05/2009 Boyd Stephen Smith Jr. wrote: > In <20090526113058.ga5...@resivo.wgnet.de>, Jonas Meurer wrote: > >On 25/05/2009 Russ Allbery wrote: > >> More concerning is the last symbol removal, which indicates that the > >> library has removed: > >> > >> DwString::operator[](unsigned

Re: how to check for binary compability?

2009-05-26 Thread Boyd Stephen Smith Jr.
In <20090526113058.ga5...@resivo.wgnet.de>, Jonas Meurer wrote: >On 25/05/2009 Russ Allbery wrote: >> Jonas Meurer writes: >> > -_ZN8DwStringixEm > >i don't understand that one at all. I cannot find anything with the >string 'ZN8DwStringixEm' in either kdepim or kdelibs sources. It wouldn't. It

Re: how to check for binary compability?

2009-05-26 Thread Jonas Meurer
Hey, First thanks for your very valuable answers, they helped me a lot. On 25/05/2009 Russ Allbery wrote: > Jonas Meurer writes: > > > At packaging mimelib1 from standalone-source I patched the sources to > > use strncpy/strncat instead of strlcpy/strlcpy along with several > > other changes. >

Re: how to check for binary compability?

2009-05-25 Thread Sune Vuorela
On 2009-05-25, Russ Allbery wrote: > The new version of the library is no longer exporting its internal > portability functions. This is good -- libraries should not export Only lurker is using this library. /Sune -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a sub

Re: how to check for binary compability?

2009-05-25 Thread Russ Allbery
Jonas Meurer writes: > At packaging mimelib1 from standalone-source I patched the sources to > use strncpy/strncat instead of strlcpy/strlcpy along with several > other changes. > > Now I tried to check for binary compability with libmimelib1c2a packages > from kdepim 3.5.9 sources. To do that, I

how to check for binary compability?

2009-05-25 Thread Jonas Meurer
Hello again, This is the third time I'm writing to debian-mentors. I don't know why nobody replied to my former mails, but maybe I didn't describe the problem good enough, or the answers to my questions where to obvious. At packaging mimelib1 from standalone-source I patched the sources to use st