[QUICK] talloc bugs
Volker.Lendecke at SerNet.DE
Wed Jul 1 13:05:27 GMT 2009
On Wed, Jul 01, 2009 at 10:53:44PM +1000, tridge at samba.org wrote:
> > 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.
> That is the job of the shared library package maintainer, not us. I
> know that you and Jelmer have been doing the work behind that library
> maintainence, but that is not a reason to prevent ABI changes within
Ok, then lets rename talloc and all callers inside Samba.
Otherwise we sooner or later will end up linking in a
library that itself links in an incompatible system talloc
which then will overwrite our internal symbols.
Everything else will be a huge mess. I know what I'm talking
about, I've tried to ship a statically linked Kerberos
library in times when the system-supplied ones were not
doing HMAC-MD5. This is just a horrendous desaster.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/samba-technical/attachments/20090701/4c3d921f/attachment.bin
More information about the samba-technical