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

[Morgan Tocker]

Hi Robie,

> 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.

Understood.  The reason I had suggested this was that in the process of reconciling we may create more problems if the scope of users affected was minimal.

> 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.

This is the ideal first solution to evaluate.  After Norvald (and repo team) have analyzed the impact the incompatibilities have, we can offer more advice on how to handle it.

- Morgan