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

Hi Sergei,

Good day!

On Tue, Nov 11, 2014 at 12:02 PM, Sergei Golubchik <[email protected]> wrote:
> 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.
>

This's very cool! MySQL should also take it.
Hmmm... "MariaDB is a drop-in replacement for MySQL." I should look at
it and probably use in the future. :-P

> 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.
>

Yes, I like the idea. I think self-encapsulation makes a lot of sense
and much easier to manage (e.g., find stuff) for people like me.

> Regards,
> Sergei



-- 
Tianyin XU,
http://cseweb.ucsd.edu/~tixu/

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