From: Michael S. <msa...@pc...> - 2005-10-28 15:42:53
|
I've had a few questions about this-- sorry my previous email wasn't clearer: When you first download/checkout GUS, you will have a project_home with the install component that contains gus.config.sample. You must manually copy this to gus_home/config/gus.config and edit it as appropriate before running the installer. All GUS components now use that as a single point of configuration. $GUS_HOME/config/gus.config will never be overwritten since there's no automatic process to copy it. $PROJECT_HOME/install/gus.config will never be read since it's an deprecated configuration method. There is ONLY ONE configuration file!! $GUS_HOME/config/ gus.config It is created manually. All other gus.config or gus.property files are ignored!! Hope this is more clear :) Mike On Oct 28, 2005, at 11:36 AM, Junmin Liu wrote: > Hi, Mike, > > >> ****** All GUS configuration* now comes from $GUS_HOME/config/ >> gus.config. $GUS_CONFIG_FILE is no longer used anywhere in the >> codebase. >> >> $GUS_HOME/config/gus.config is created at build time from >> $PROJECT_HOME/install/gus.config. Thus, you should make changes >> > > Will $GUS_HOME/config/gus.config be overwritten every time we > change the $PROJECT_HOME/install/gus.config? I think months ago I > complained about this bug (http://sourceforge.net/mailarchive/ > message.php?msg_id=11820770), and you said it is feature not a bug. > > So is it still a feature now, which is the $GUS_HOME/config/ > gus.config will not be overwritten after being genetated? > > ---junmin > |