[debian-mysql] ABI break between 5.5 and 5.6?

[Robie Basak]

Hi Morgan,

Thank you for replying so quickly.

> The followup question of course is if the breakage has a direct effect
> on Debian applications.  We may actually be lucky in this instance,
> and the incompatibility is limited in scope.  If there are issues,
> what we may be able to do is effectively reserve libmysqlclient.so.19
> for Debian to reconcile the problem.  This is something to discuss.

OK, so what do we do now?

I think this issue extends beyond Debian and Ubuntu because of users'
binary compatibility assumptions. Consider a user bringing in a binary
exectuable built somewhere else (another distribution, or built by hand
against your published source or binaries). This user expects certain
behaviour, and this behaviour will change on a switch to 5.6.

The same applies vice versa. If I build a binary on Debian or Ubuntu
that links against libmysqlclient.so.18, I expect it to work against any
other system's libmysqlclient.so.18 regardless of whether that system
has been built against 5.5, 5.6, from a distribution, or directly from
upstream.

So whatever we do, I think we need to agree and follow the same path. I
don't think it's a case of reserving libmysqlclient.so.19 just for
Debian; it's a case of coordinating the same soname bump for everyone.

On the other hand, we might be able to pragmatically conclude that
nobody will be affected, so no action is needed. Then the bugs would
effectively be "Won't Fix" with the enum one remaining fundamentally
unfixable for the lifetime of 5.6.

Robie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20140910/99e9eebe/attachment.sig>