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

[Norvald H. Ryeng]

On Wed, 17 Sep 2014 21:44:21 +0200, Otto Kekäläinen <otto at seravo.fi> wrote:

> 2014-09-16 17:31 GMT+03:00 Norvald H. Ryeng <norvald.ryeng at oracle.com>:
>> We have a preliminary analysis. There are still a few details to
>> examine, but I believe we have a result we can share now. It may change
>> if the details turn out to be not exactly as expected, though.
>
>
> A simple question: why does not the mysql-5.x packages have a
> debian/libmysqlclient18.symbols file as the Debian policy recommends?
> It would have helped spot these issues long time ago.. It is not too
> late to start having one.

It's too late for 5.6. Shrinking the list of exported symbols is an  
incompatible ABI change that requires a major version bump. It's also an  
API change, so it might require more than just a rebuild of clients.

For future versions, this is a very good idea. Restricting it to the  
official, documented API is easy, but there are a few undocumented  
functions that are used by clients. We still haven't decided exactly what  
to do with these. We either have to add them to the official API or find  
workarounds for clients.

Norvald