[debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

Otto Kekäläinen otto at seravo.fi
Mon Apr 11 20:15:54 UTC 2016


2016-04-08 16:28 GMT+03:00 Robie Basak <robie at justgohome.co.uk>:
> 1. If we have MariaDB packaging provide the/a client library for
> depending packages, then I think that should be under a different soname
> to prevent collisions. Otherwise confusion will ensue as MySQL upstream
> carry on with new libmysqlclient.so sonames.

It does not make sense to provide a different soname, as that would
require changes in other programs sources to use the different name. I
think mariadb-10.0 source should provide a libmariadbclient18 binary
package that conflicts with the mysql-5.6 one and provides the library
file using the name libmysqlclient.so.18

> 2. I'm not sure it makes sense for MariaDB packaging to provide a fork
> of libmysqlclient.so.18 even under a different soname. Given that
> MariaDB upstream have deprecated this, upstreams aren't likely to
> maintain compatibility with it. They'll either move on to building
> against MySQL 5.7 and its libmysqlclient.so.20, or they'll move to
> MariaDB's solution of building against their new library.

MariaDB has not deprecated the client library. It should be fully
backwards compatible and provide some extra benefits, like support for
event based flows. It is worth providing and worth using.

> So I think (please correct me if I'm wrong):
> 1. mysql-common: consensus is to split into a separate source package.
> 2. Dependencies on mysql-{client,server}: consensus is to have depending
> packages depend on mariadb-{client,server} as a first alternative with
> virtual-mysql-{server,client} as a second.
> 3. libmysqlclient: needs further discussion.

Ok, let's now proceed with 1 and 2 as we agree on those and then
return to the libmysqlclient.so.18 discussion later.

More information about the pkg-mysql-maint mailing list