-fi
-
-# patch home to undo cygwin style of drive letter.
-export HOME=$(echo $HOME | sed -e 's/\/cygdrive\//\//g')
-#echo HOME is now $HOME
-
-if [ "$OS" == "Windows_NT" ]; then
- export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
-fi
-
-# ulimit and umask. umask sets a permission mask for all file
-# creations. The mask shown here disallows writing by the "group" and
-# "others" categories of users. ulimit sets the user limits. the core
-# file size is set to zero.
-umask 022
-ulimit -c 0
-
-##############
-
-# Directory variables...
-
-export SCRIPT_SYSTEM=feisty_meow
-
-#if [ -z "$FEISTY_MEOW_DIR" ]; then export FEISTY_MEOW_DIR="$HOME/$SCRIPT_SYSTEM"; fi
-#if [ -z "$FEISTY_MEOW_SCRIPTS" ]; then export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_DIR/scripts"; fi
-#if [ -z "$FEISTY_MEOW_SCRIPTS" ]; then export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_SCRIPTS"; fi
-
-# include helpful functions.
-source "$FEISTY_MEOW_SCRIPTS/core/functions.sh"
-
-# LIBDIR is an older variable that points at the root of the yeti code.
-export LIBDIR=$FEISTY_MEOW_DIR
-
-if [ -z "$FEISTY_MEOW_GENERATED" ]; then
- # The generated scripts directory is where automatically generated files live.
- # It is separate from the main body of the shell scripts in order to keep things from
- # exploding.
- export FEISTY_MEOW_GENERATED=$HOME/.zz_auto_gen
-fi
-
-##############
-
-# user variables...
+
+ # similarly, make sure we have someplace to look for our generated files, if
+ # we were not handed a value.
+ if [ -z "$FEISTY_MEOW_GENERATED" ]; then
+ # The generated scripts directory is where automatically generated files live.
+ # It is separate from the main body of the shell scripts in order to keep things from
+ # exploding.
+ export FEISTY_MEOW_GENERATED=$HOME/.zz_auto_gen
+ fi
+
+ ##############
+
+ # umask sets a permission mask for all file creations. the mask used here
+ # disallows writing by the "group" and "others" categories.
+ umask 022
+ # ulimit sets user limits. we set the maximum allowed core dump file size
+ # to zero, because it is obnoxious to see the core dumps from crashed
+ # programs lying around everywhere.
+ ulimit -c 0
+
+ ##############
+
+ # user variables, sort of... if they haven't given themselves a name yet,
+ # then we will make one up for them.
+
+ # define a default name, if one wasn't already set.
+ if [ -z "$NAME" ]; then
+ export NAME='Unset Q. Namington, Fixley Your Name III'
+ fi
+
+ ##############
+
+ # variables for perl.
+
+ export PERLLIB
+ if [ "$OS" != "Windows_NT" ]; then
+ PERLLIB+="/usr/lib/perl5"
+ else
+ export PERLIO=:perlio
+ # 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
+ if [ -d "$i" ]; then
+ # check if there is a perl file present; add the folder to PERLLIB if so.
+ ls $i/*.pl &>/dev/null
+ if [ $? -eq 0 ]; then
+ PERLLIB+=":$i"
+ fi
+ fi
+ done
+ #echo PERLLIB is now $PERLLIB
+
+ ##############
+
+ # set this so nechung can find its data.
+ export NECHUNG=$FEISTY_MEOW_DIR/database/fortunes.dat
+
+ # ensure we use the right kind of secure shell.
+ export CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
+ export GIT_SSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
+
+ # the base checkout list is just to update feisty_meow. additional folder
+ # names can be added in your customized scripts.
+ export REPOSITORY_LIST="feisty_meow"
+
+ # initializes the feisty meow build variables, if possible.
+ function initialize_build_variables()
+ {
+ found_build_vars=0
+ # we need to know the feisty meow directory, or we bail.
+ if [ -z "$FEISTY_MEOW_DIR" ]; then return; fi
+ # pick from our expected generator folder, but make sure it's there...
+ buildvars="$FEISTY_MEOW_DIR/scripts/generator/build_variables.sh"
+ if [ -f "$buildvars" ]; then
+ # yep, that one looks good, so pull in the build defs.
+ source "$buildvars" "$buildvars"
+ found_build_vars=1
+ fi
+ # now augment the environment if we found our build variables.
+ if [ $found_build_vars == 1 ]; then
+ # the binary directory contains handy programs we use a lot in yeti. we set up the path to it
+ # here based on the operating system.
+ # note that yeti has recently become more dependent on hoople. hoople was always the source of
+ # the binaries, but now we don't ship them with yeti any more as pre-built items. this reduces
+ # the size of the code package a lot and shortens up our possible exposure to compromised
+ # binaries. people can bootstrap up their own set from hoople now instead.
+ export BINDIR=$FEISTY_MEOW_DIR/production/binaries
+
+ # add binaries created within build to the path.
+# export PATH="$(dos_to_msys_path $BUILD_TOP/build/bin):$PATH"
+ export PATH="$BINDIR:$PATH"
+
+ # Shared libraries are located via this variable.
+# export LD_LIBRARY_PATH="$(dos_to_msys_path $LD_LIBRARY_PATH):$(dos_to_msys_path $BINDIR)"
+ export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$BINDIR"
+ fi
+ }
+
+ ##############
+
+ # windoze specific patching up missing things.
+
+ if [ "$OS" == "Windows_NT" ]; then
+ export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
+ fi
+
+ ##############
+
+ # load in the build environment.
+ initialize_build_variables
+
+ ##############
+
+ # set the path for locating applications. this is done after any
+ # potential overrides from the user.
+ #export PATH="$(dos_to_msys_path $BINDIR):$(dos_to_msys_path $FEISTY_MEOW_GENERATED):$PATH:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/lib:/usr/games:/usr/bin:."
+ export PATH="$FEISTY_MEOW_GENERATED:$PATH:/sbin:."
+###noise! :/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/lib:/usr/games:/usr/bin:.
+
+ ##############
+
+ # set the SHUNIT_DIR so our shunit tests can find the codebase.
+ export SHUNIT_DIR="$FEISTY_MEOW_SCRIPTS/shunit"
+
+ ##############
+
+ if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi