[debian-mysql] percona vs. mariadb

[Clint Byrum]

Excerpts from Steven Ayre's message of 2013-03-07 04:48:45 -0800:
> +1 too, much like there are multiple options for the MTA.
> 
> Two packages that're likely to cause a problem are:
> mysql-common (ships my.cnf which may not be compatible across all versions)
> libmysqlclientXX
> 

We should just ship the same major.minor release of all of them if
they're going to share /etc/mysql/my.cnf.

I'd prefer, though, that they didn't if at all possible. If they must,
this probably means having them conflict and provide so that incompatible
options don't cause issues.

> There're a number of mysql variants that it might be useful to support:
> mysql community server

Just to be clear, thats what we have now.

> mysql cluster

Was in Debian before, and dropped

> percona server
> mariadb
> galera

-1 for the Galera patched MySQL. I think thats going to lag too much
behind MySQL proper. I'd much rather see this folded into mariadb and/or
percona-server.

Having all of these mean a really crazy amount of effort whenever there
is a security bug.

Perhaps we should just let the others ship from their own apt repo's,
and pick one that serves all of the users with the least amount of
surprise and work for our very limited maintenance team.

To be honest, thats still Oracle's MySQL. :-P

If Percona, MontyProgram, or SkySQL are interested in Debian's archive
as a distribution mechanism, I suggest they commit resources to that.