[QUICK] talloc bugs

[Jelmer Vernooij]

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

Hi Tridge,

tridge at samba.org wrote:
> Hi Simo,
>
>  > So, no, not all APIs or ABIs inside samba are changeable at will at this
>  > point. That doesn't mean they are locked down, just that a change that
>  > breaks the API contract or the ABI interface need to be evaluated and
>  > agreed upon in advance and decisions need to be made on whether this
>  > warrant creating a new set of libraries (basically a fork and rename of
>  > symbols), or whether the extensions required can be done without
>  > breaking existing code.
>
> As regards to the API changes I made (disallowing some previously
> ambiguous operations), that is a bug fix. Disallowing previously buggy
> usage is quite normal between versions of libraries as far as I know,
> just like bug fixing is normal between library versions.
>
> 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.

As package maintainers, we'll then deal with this and make sure
packages with the new sonames are available (as well as with the old
soname, if there's a reason for that). Of course, we would like to
avoid this situation when it's not really necessary because it causes
extra work.

Cheers,

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

iJwEAQECAAYFAkpLY0EACgkQDLQl4QYPZuUPGwQAgsDLV1iZUUIxwly80F5u/c9X
0gwE0l9BbaLbcKEpD56TDiitpn6zbY18TJa5wXcg7a/tAqPS3JYabo1PExxSGu+C
rV1A05zkxRWSHDSkZ8ICmSxheKwdmJ3oERIR1lNo6ZHkGvDAiXZVoBvs8VfJ0Btf
uVs3McUkOn7jTttQ7YI=
=vQe2
-----END PGP SIGNATURE-----