[debian-mysql] my.cnf problems

[Clint Byrum]

Excerpts from Bjoern Boschman's message of 2013-12-06 06:01:19 -0800:
> Hi folks,
> 
> I've seen some blockers due to the fact that everybody (mysql, maria,
> percona) includes my.cnf from mysql-common.
> 
> my 2 cent:
> 
> maria: /etc/mariadb/my.cnf
> mysql: /etc/mysql/my.cnf
> percona: /etc/percona/my.cnf
> 
> From my point of view it's a dream that cannot be fullfilled that all
> forks can share the same configuration file.
> 

This dream is one propagated by all three. They hard code /etc/mysql
everywhere.

This is complicated further by libmysqlclient also hard coding the path.

Your idea is great, but so far, none of them will work this way.

What we can do is strive to make /etc/mysql/my.cnf ONLY fully
compatible command line options. We can use server specific files in
/etc/mysql/conf.d for non-compatible options. Anything that simply has
to be in /etc/mysql/my.cnf can probably be specified with 'loose-option'
but I'd prefer to avoid that if we can.

It should be fine for leaf packages like mariadb-server-5.5 and
mysql-server-5.6 to have 'breaks' directives for each other. They likely
want to be on port 3306 by default too, so this makes perfect sense. Also
the -core packages which just get you the binaries can be free of these
config files, since they are generally only useful in situations where
you do want the two different implementations to live together.