Menu
▾
▴
gusdev-gusdev
|
From: Michael S. <msa...@pc...> - 2005-10-28 02:06:04
|
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) |
|
From: Michael S. <msa...@pc...> - 2005-10-28 13:59:36
|
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 > |
|
From: Deborah P. <pi...@pc...> - 2005-10-28 14:06:32
|
Michael Saffitz wrote: >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. > > This should be done manually? build = install ? >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 >> >> >> > >_______________________________________________ >ApiDB mailing list >Ap...@pc... >https://mail.pcbi.upenn.edu/mailman/listinfo/apidb > > |
|
From: Michael S. <msa...@pc...> - 2005-10-28 14:18:06
|
Yes, this will be done manually. In 3.5 this file was manually created from gus.config.sample in install. Now, it's exactly the same, it's just manually created in a new spot (in $GUS_HOME, not in $PROJECT_HOME). I'll move all further discussion to gusdev so folks don't keep getting repeats of emails. --Mike On Oct 28, 2005, at 10:04 AM, Deborah Pinney wrote: > Michael Saffitz wrote: > > >> 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. >> >> > This should be done manually? build = install ? > > >> 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 >>> >>> >>> >> >> _______________________________________________ >> ApiDB mailing list >> Ap...@pc... >> https://mail.pcbi.upenn.edu/mailman/listinfo/apidb >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Gusdev-gusdev mailing list > Gus...@li... > https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev > |
|
From: Junmin L. <ju...@pc...> - 2005-10-28 15:37:10
|
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 |
|
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 > |
|
From: Y. T. G. <yg...@pc...> - 2005-10-28 16:52:59
|
On a fresh $GUS_HOME (possibly first attempt to install GUS software and the user is new to GUS), the GUS installer will simply complain that $GUS_HOME/config/gus.config does not exist. I have checked in a fix to the GUS installer to give explicit instruction on what to do when that happens (copying from the sample file and make appropriate edits if necessary). -Thomas > -----Original Message----- > From: gus...@li... > [mailto:gus...@li...] On Behalf > Of Michael Saffitz > Sent: Friday, October 28, 2005 10:43 AM > To: Junmin Liu > Cc: Gusdev gusdev-gusdev; ApiDB Project Mailing List; cbil > cb...@pc... > Subject: [GUSDEV] Re: [CBIL] GUS Config Changes > > > > 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 > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through > End of 2005 Visit http://www.jboss.com/services/certification > for more information _______________________________________________ > Gusdev-gusdev mailing list > Gus...@li... > https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev > |
|
From: Junmin L. <ju...@pc...> - 2005-10-28 15:49:13
|
I see. I think my previous email said: "$GUS_HOME/config/gus.config is created at build time from $PROJECT_HOME/install/gus.config." It just confused me. Probably we should say, "Manually created $GUS_HOME/config/gus.config, using gus.config.sample in project_home as an example". --junmin On Fri, 28 Oct 2005, Michael Saffitz wrote: > > 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 >> > |
|
From: Junmin L. <ju...@pc...> - 2005-10-28 15:55:42
|
> I see. I think my previous email said: "$GUS_HOME/config/gus.config is a typo: "my previous email" should be "your previous email". > created at build time from $PROJECT_HOME/install/gus.config." It just > confused me. > > Probably we should say, "Manually created $GUS_HOME/config/gus.config, > using gus.config.sample in project_home as an example". > > --junmin > > > > On Fri, 28 Oct 2005, Michael Saffitz wrote: > >> >> 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 >>> >> > _______________________________________________ > CBIL mailing list > CB...@pc... > https://mail.pcbi.upenn.edu/mailman/listinfo/cbil > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X