[debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*
otto at seravo.fi
Mon Apr 11 20:38:52 UTC 2016
2016-03-23 23:44 GMT+02:00 Emilio Pozuelo Monfort <pochu at debian.org>:
> We decided to make mariadb the default provider. That would mean having mariadb
> as the default alternative in packages relationships, or have mariadb provide
> something à la default-mta. We'd also need a solution for libmysqlclient, unless
> that could be (eventually) split off mysql in case that came to be necessary.
> I suggest we make a plan for this, then send it to debian-devel@ before the MBF
> Can you suggest a plan to make the necessary changes?
The pkg-mysql-maint team discussed this. We don't have agreement on
everything, like how to ship the libmysqlclient.so.18 library, but
let's now proceed with the parts that we have agreement on as follows:
1. MariaDB as default
We shall not invent a new metapackage, but instead leverage on the
existing virtual-mysql-server/cllient package scheme. It was agreed
upon already back in 2013 and all upstreams and downstreams to date
follow the convention (including MariaDB, Percona, Oracle and even
mysql-wsrep). This scheme is both backwards compatible and future
proof if users combine vanilla Debian repositories with external
repositories. Using the existing scheme requries least effort to
extend, and as it involves least amount of change it is technically
also least risky in terms of regressions or other problems.
As so, we now propose to mass file bugs about packages in Debian that
currently depend on mysql-* to depend on mariadb-* | virtual-mysql-*
instead. If nobody objects, I'll write about the intent to mass file
bug to debian-devel in a few days and then actually file the bugs in
I have already documented it here:
2. mysql-common and configuration
Both packages mysql-5.6 and mariadb-10.0 use mysql-common from
mysql-5.6. It will be split into a separate source package that is
independent of the mysql-5.6 source package (or any later version).
Andreas B: Can you make an action point to yourself about issue 2? It
would help a lot if I am not alone responsible of implementing all
The pkg-mysql-maint team will continue to discuss this issue and get
back later with a suggestion on how to do it.
More information about the pkg-mysql-maint