##############
# we'll run this again only if we think it's needed.
-if [ -z "$NECHUNG" ]; then
+if [ -z "$CORE_VARIABLES_LOADED" ]; then
if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization begins...; fi
fi
# set up the top-level for all build creations and logs and such.
- if [ -z "$GENERATED_DIR" ]; then
- define_yeti_variable GENERATED_DIR="$TMP/generated-feisty_meow"
+ if [ -z "$GENERATED_STORE" ]; then
+ define_yeti_variable GENERATED_STORE="$TMP/generated-feisty_meow"
fi
- if [ ! -d "$GENERATED_DIR" ]; then
- mkdir -p "$GENERATED_DIR"
+ if [ ! -d "$GENERATED_STORE" ]; then
+ mkdir -p "$GENERATED_STORE"
fi
# set up our effluent outsourcing valves.
- if [ -z "$TEMPORARIES_DIR" ]; then
- define_yeti_variable TEMPORARIES_DIR="$GENERATED_DIR/temporaries"
+ if [ -z "$TEMPORARIES_PILE" ]; then
+ define_yeti_variable TEMPORARIES_PILE="$GENERATED_STORE/temporaries"
fi
- if [ ! -d "$TEMPORARIES_DIR" ]; then
- mkdir -p "$TEMPORARIES_DIR"
+ if [ ! -d "$TEMPORARIES_PILE" ]; then
+ mkdir -p "$TEMPORARIES_PILE"
fi
# similarly, make sure we have someplace to look for our generated files, if
fi
##############
+
+ # set up the color_add variable which is a flag that lets ls know colors work.
+
+ # test if we can use color in ls...
+ ls --help 2>&1 | grep -i -q color
+ if [ $? -eq 0 ]; then
+ export color_add='--color=auto'
+ else
+ export color_add=
+ fi
+ unset test_ls_colors
+ ##############
+
# umask sets a permission mask for all file creations.
# this mask disallows writes by "group" and "others".
umask 022
# choose perl's IO over the ms-windows version so we can handle file
# bytes properly.
fi
-
+
# iterate across our sub-directories and find the perl scripts.
# this currently only looks one level down.
for i in $FEISTY_MEOW_SCRIPTS/*; do
# set this so nechung can find its data.
define_yeti_variable NECHUNG=$FEISTY_MEOW_APEX/infobase/fortunes.dat
+## # establish a pipe for less to see our beloved syntax highlighting.
+## define_yeti_variable LESSOPEN="| source-highlight -f esc -o STDOUT -i %s"
+
# ensure we use the right kind of secure shell.
# define_yeti_variable CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
# define_yeti_variable GIT_SSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
# now augment the environment if we found our build variables.
if [ $found_build_vars == 1 ]; then
# the binary directory contains our collection of handy programs.
- define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_DIR
+ define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_STORE
# add binaries created within build to the path.
define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_BINARIES):$PATH"
# Shared libraries are located via this variable.
##############
- # set the SHUNIT_DIR so our shunit tests can find the codebase.
- define_yeti_variable SHUNIT_DIR="$FEISTY_MEOW_SCRIPTS/shunit"
+ # set the SHUNIT_PATH so our shunit tests can find the codebase.
+ define_yeti_variable SHUNIT_PATH="$FEISTY_MEOW_SCRIPTS/shunit"
##############
+
+ define_yeti_variable CORE_VARIABLES_LOADED=true
if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi
fi
fi
source "$i"
done
-
+