On Wed, Jan 30, 2013 at 9:24 PM, Pascal Giard <evily...@gmail.com> wrote:
> On Wed, Jan 30, 2013 at 9:52 PM, Pascal Giard <evily...@gmail.com> wrote:
> > That being said, it would help me if you could tell me if a new symbol
> > was introduced or an existing one modified in 14.4.1.
> > See [1] for details on what constitutes an ABI change.
> >
> > I don't know if I can automate that verification, I would assume there
> > must be a way to at least partly automate this. Otherwise maintaining
> > big unstable shared libraries would be a nightmare.
> >
> > Cheers,
> >
> > -Pascal
> > [1]
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-updates
>
> Answering to my own email, dpkg-gensymbols is the tool to use for symbols.
> Unless I'm not using it properly, there is no symbol change introduced
> in 14.4.1.
>
> However, that doesn't necessarily mean that 14.4.1 is binary
> compatible with 14.4.0.
> Some changes can not be catched by checking symbols e.g. a struct that
> changed size.
>
> Do you know if there has been a change that could break binary
> compatibility?
>
> Cheers,
>
For SoX, you should be able to get an idea of API and ABI modifications
using "git log -u src/sox.h" since that defines our interface to library.
That shows no modifications in dot branch since 14.4.0 release.
I'll have to read up on this new approach. Is it OK to ignore API/ABI
changes related to internal-only symbols that we are allowing to leak out
(those prefixed with lsx_)?
Chris
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
