[mythtv] Re: [PATCH] Stop make install from overwriting mysql.txt

Gavin Hurlbut gjhurlbu+mythtv-dev at beirdo.ca
Wed Oct 6 03:01:09 UTC 2004


Joseph A. Caputo <jcaputo1 at comcast.net> wrote:
> ...except that it's not just a 'system-wide' config.  You could have 
> different users specifying a different DBHostName, so that each user 
> would get their own personal frontend settings when they run.  Or you 
> could even have different users specifying completely different 
> databases (if, for instance, you had 2 completely separate backend 
> setups, say, testing & production) and hence using different backends.  
> When viewed this way, mysql.txt is just like any other application 
> configuration file:  a master copy resides in a common location and is 
> used if no per-user copy is found.

Good points.  I doubt that many of those setups are common, but good points.
As for your last statement, that is correct, but with one caveat: the "master
copy" is overwritten at every install. :)


Anyways, I'm moving on.  I've sent rkulagow a patch to make the documentation
more consistent and obvious, highlighting that the preferred option is to
use ~/.mythtv/mysql.txt in all three places it's mentioned, and indicated why.
Hopefully that makes it in.


I don't have the energy nor the desire to argue this to death when Isaac's
made it obvious that it isn't going to change anyways.  I have enough other
things to spend my spare time on :)

Ciao
Gavin



More information about the mythtv-dev mailing list