[GUSDEV] Re: [CBIL] GUS Config Changes

[Michael S. <msa...@pc...>]

One additional change:

At install time, $PROJECT_HOME/install/gus.config.sample should be  
moved and configured to $GUS_HOME/config/gus.config.  This file (in  
$GUS_HOME) will then be the sole configuration for GUS.

No components in GUS will use $PROJECT_HOME/install/gus.config  
anymore, nor will it automatically be copied to $GUS_HOME/config/ 
gus.config

--Mike

On Oct 27, 2005, at 10:05 PM, Michael Saffitz wrote:

>
> All,
>
> I've finally fixed the long standing and often confusion generating
> issue of properly configuring GUS.  This change should be relatively
> minor, and full details are below, but I wanted to make sure everyone
> was clear.
>
> Short Version:
>
> ******    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
> there and do a build to move them to $GUS_HOME if you need to make
> config changes.
>
> Long Version:
>
> In 3.5, we had the gus.config file as well as the $GUS_HOME_CONFIG
> file.  The latter was generated by the former, and some components
> used one while other components used the other.  It thus became
> confusion to know what configuration you were actually using, and
> there was of course redundancy.  This resolves that issue.  An
> outstanding issue remains how to provide functionality to easily
> switch between multiple configurations.
>
> *  (except when otherwise overridden on the command line)
> _______________________________________________
> CBIL mailing list
> CB...@pc...
> https://mail.pcbi.upenn.edu/mailman/listinfo/cbil
>