[OTR-dev] libotr major version bump?

Ian Goldberg ian at cypherpunks.ca
Sat Jul 28 14:14:40 EDT 2007

On Fri, Jul 27, 2007 at 07:56:39PM -0400, Greg Troxel wrote:
> Was this really necessary?  Upgrading to 3.1.0 from 3.0.0 went from 2.0
> to 3.0 in ELF shlib numbering, and I see nothing in NEWS that indicates
> why - just things that look like they might have new calls, vs changing
> the signature of existing calls.  So the gaim-otr for gaim 1.5 was
> broken by this.  NEWS really should say clearly which procedures had an
> interface change, so that users of the library can update their code.
> Rebuilding gaim-otr seems to fix the problem, though, so there seems not
> to have been an API change.

That's weird.  When I build libotr-3.1.0, I get a "libotr.so.2.1.0", as
expected, since the API and ABI are indeed back-compatible.

libotr's configure.ac indicates:


which specifies current=3, revision=0, age=1, so you get 2.1.0 out of

What version number is libtool using for you?

libotr's UPDATING file contains the information about how users of
libotr can update their code for the new version.

   - Ian

More information about the OTR-dev mailing list