windows build and r15912

[Andreas Köhler]

Hi,

very good point, Kevin.  Somehow I forgot about it.
Derek, that is almost exactly what I am going to implement now.  The 
head of defaults should explain it once I have it running and committed.

-- andi5

Derek Atkins schrieb:
> Perhaps we should pull in custom.sh first, and then have
> defaults.sh do something like:
> 
> [ -z "${GLOBAL_DIR:-}" ] && GLOBAL_DIR=<default>
> 
> .. and do this for all the variables to only set them if
> they are not already set.
> 
> -derek
> 
> "Hale Boyes, Kevin " <Kevin.HaleBoyes at encana.com> writes:
> 
>> Maybe my scripting skill are a bit rusty but how is the
>> new defaults/custom file loading going to work?
>>
>> The only value that I normally change is the GLOBAL_DIR setting.
>> When I create the custom file, will it contain just the GLOBAL_DIR
>> variable or do I need to copy the entire defaults file and
>> change just the one variable?
>>
>> I'm guessing that I need to do the later because of all the
>> variables that depend on the value of GLOBAL_DIR (like DOCS_DIR).
>> They will be set before the custom file is sourced and their
>> value won't change when I reset the value of GLOBAL_DIR.
>>
>> Hmm, I guess I'll have to be more careful than that.  I won't
>> want an exact copy of defaults as that would call all the add_step
>> functions again.
>>
>> In an attempt to answer my own question...  If I want to change the
>> value of GLOBAL_DIR then I will put it and all the variable that
>> depend on it into the custom file, but nothing else.  It isn't enough
>> to put just GLOBAL_DIR into custom.
>>
>> Is that correct?
>>
>> Thanks,
>> Kevin.