[QUICK] talloc bugs
idra at samba.org
Wed Jul 1 13:30:51 GMT 2009
On Wed, 2009-07-01 at 15:28 +0200, Volker Lendecke wrote:
> On Wed, Jul 01, 2009 at 03:23:18PM +0200, Jelmer Vernooij wrote:
> > > The shared library package maintainer might decide to change the major
> > > version as a result, and that would be a perfectly valid reaction, but
> > > to say we can't change code inside Samba is far too constraining on
> > > the project.
> > Changing the version number/soname should happen in the upstream
> > project when the ABI is changed. This should also make sure we don't
> > end up linking against outdated system versions of talloc.
> How do you deal with libraries you link against that
> themselves link in the system libs?
> The example I had is libldap->libkrb5. That just broke all
> the symbols I had carefully linked in statically into
The only *non portable* way, in linux is to use symbol versioning
instead of soname bumps. But this requires keeping compatibility code in
the library as well.
The best way, of course, would be to avoid breaking the ABI when there
is no technical need.
Samba Team GPL Compliance Officer <simo at samba.org>
Principal Software Engineer at Red Hat, Inc. <simo at redhat.com>
More information about the samba-technical