[debian-mysql] my.cnf in mysql-server instaed of mysql-common

[Christian Hammers]

On Wed, 20 Feb 2008 12:21:06 -0300
Monty Taylor <monty at inaugust.com> wrote:

> Monty Taylor wrote:
> 
> >> If I wanted to run multiple binaries I would have to pass separate configs
> >> to each of them anyway.
> >>
> >> So I don't see the problem right now...
> > 
> > Well, mysql looks in /etc/mysql/my.cnf by default now too. So they don't
> > install any mysql packages,  but mysql-common probably gets installed
> > due to a depend somewhere, and then then install their tarball and all
> > of a sudden it's reading settings that they aren't expecting.
> 
> What if we put an /etc/mysql/my.cnf in mysql-common that just includes
> /etc/mysql/conf.d, and then have mysql-client install an
> /etc/mysql/conf.d/mysql-client and mysql-server install an
> /etc/mysql/conf.d/mysql-server?

libmysqlclient also depends on mysql-common for the reason that all
client scripts like PHP/Perl programs should know which socket/port to 
connect to.

This means mysql-common would have to provide /etc/mysql/conf.d/mysql-client
and that means that a user with a "mysql binary distribution" would still
face the problem that his client programs try to connect to the socket in
the default Debian location. 

So do we win enough to justify the work for those couple of users?

Maybe it's easier if you add a patch to mysqld that prints which config
files it read when it starts up :)

bye,

-christian-