Re: What led to the design of having multiple option file locations?

Hi, Tianyin!

On Nov 11, Tianyin Xu wrote:
> Thanks a lot for the explanation, Stewart and Sergei!
> 
> Basically the main purpose is to support different conventions such as
> Redhat- and Debian-based distributions.
> 
> Wait... Isn't this a bad way to do things? I think the right way is to
> decide at installation time: figure out the type of system and decide
> the location of the configuration file. This makes even less sense
> when using pre-compiled mysql packages for specific distribution
> (e.g., the ones dedicated for Fedora and Ubuntu via yum or apt-get).

Agree! And we've fixed it in MariaDB few months ago.

I've implemented an option to compile out these standard paths, and this
is now used in our RPM packages. MariaDB only reads /etc/my.cnf, not
/etc/mysql/my.cnf.

The main reason was to be able to compile MariaDB
into a certain path (e.g. /opt/mariadb-10/) and make sure it does not
read any cnf files outside of it.

Regards,
Sergei

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    http://lists.mysql.com/internals