[QUICK] talloc bugs

Jelmer Vernooij jelmer at samba.org
Wed Jul 1 13:33:27 GMT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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 heimdal.
Symbol versioning is the only real way to deal with that, indeed.

Would this really be a problem though? We don't rely on any system
libraries that use talloc (yet), so I think we should be fine until we do.

Cheers,

Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkpLZaMACgkQDLQl4QYPZuUTAAP+MBGZ0ke9VAtygNC3bJ604ZL5
TeJygQZdCsyEvvuhAtd6BoSqtIE4+1AA8YMGeqPjdtinpuM3dOhCMcllb98yHa+s
I6q2bHwaFOW1poVeGnOgLzl4lpgzgi72RbCirooQs+Phx/ZfOKu6CSILA1V3ZnX4
BaPhyACZvgdq61PTZ0Y=
=b3gT
-----END PGP SIGNATURE-----



More information about the samba-technical mailing list