##############
-# System variables...
+# start with some simpler things.
+
+export SCRIPT_SYSTEM=feisty_meow
# OS variable records the operating system we think we found.
if [ -z "$OS" ]; then
fi
export IS_DARWIN=$(echo $OSTYPE | grep -i darwin)
-if [ -z "$HOME" ]; then
- if [ "$OS" == "Windows_NT" ]; then
- export HOME=/c/home
- if [ ! -d $HOME ]; then
- mkdir $HOME
- fi
+##############
+
+# windoze sometimes needs a special home variable setup.
+if [ "$OS" == "Windows_NT" ]; then
+ # give them a default place if they don't have one already.
+ if [ -z "$HOME" ]; then
+ export HOME=c:/home
+ fi
+ # patch home to undo cygwin style of drive letter.
+# export HOME=$(echo $HOME | sed -e 's/\/cygdrive\//\//g')
+ # make the home folder if it doesn't exist yet.
+ if [ ! -d $HOME ]; then
+ mkdir $HOME
fi
+ if [ ! -z "$SHELL_DEBUG" ]; then echo HOME is now $HOME; fi
fi
##############
-# windoze specific stuff.
+# fallbacks to set crucial variables for feisty meow...
-# patch home to undo cygwin style of drive letter.
-export HOME=$(echo $HOME | sed -e 's/\/cygdrive\//\//g')
-#echo HOME is now $HOME
+# set the main root directory variable for the feisty meow codebase.
+# this is only used for extreme failure modes, when the values were not
+# pulled in from our auto-generated config.
+if [ -z "$FEISTY_MEOW_DIR" ]; then
+ if [ -d "$HOME/feisty_meow" ]; then
+ export FEISTY_MEOW_DIR="$HOME/feisty_meow"
+ export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_DIR/scripts"
+ fi
+fi
-if [ "$OS" == "Windows_NT" ]; then
- export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
+# 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
##############
-# 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 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
##############
-# Directory variables...
-
-export SCRIPT_SYSTEM=feisty_meow
-
# 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, sort of... if they haven't given themselves a name yet,
##############
-# other variables...
-
# sets the main prompt to a simple default, with user@host.
export PS1='\u@\h $ ';
+##############
+
# variables for perl.
+
export PERLLIB
if [ "$OS" != "Windows_NT" ]; then
PERLLIB+="/usr/lib/perl5"
done
#echo PERLLIB is now $PERLLIB
+##############
+
# set this so nechung can find its data.
-export NECHUNG=$LIBDIR/database/fortunes.dat
+export NECHUNG=$FEISTY_MEOW_DIR/database/fortunes.dat
# ensure we use the right kind of rsh for security.
export CVS_RSH=ssh
fi
fi
-# include variables needed for compiling hoople and using its scripts.
-if [ -z "$FEISTY_MEOW_DIR" ]; then
- if [ -d "$HOME/feisty_meow" ]; then
- export FEISTY_MEOW_DIR="$HOME/feisty_meow"
- fi
-fi
-
-# initialize the build variables, if possible.
-found_build_vars=0
-if [ ! -z "$FEISTY_MEOW_DIR" ]; then
- # first guess at using the old school bin directory.
- bv="$FEISTY_MEOW_DIR/bin/build_variables.sh"
- if [ -f "$bv" ]; then
- # the old bin directory is present, so let's use its build vars.
- source "$bv" "$bv"
+# 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
- else
- # try again with the new school location for the file.
- bv="$FEISTY_MEOW_DIR/scripts/generator/build_variables.sh"
- if [ -f "$bv" ]; then
- # yep, that one looks good, so pull in the build defs.
- source "$bv" "$bv"
- found_build_vars=1
- else
- # try once more with new school and assume we're deep.
- bv="$FEISTY_MEOW_DIR/../../scripts/generator/build_variables.sh"
- if [ -f "$bv" ]; then
- # sweet, there is something there.
- source "$bv" "$bv"
- found_build_vars=1
- fi
- fi
fi
-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="$BUILD_TOP/build/bin:$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
+}
-# augment the configuration if we found our build variables.
-if [ $found_build_vars == 1 ]; then
+# load in the build environment.
+initialize_build_variables
- # 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"
+# windoze specific patching up missing things.
- # Shared libraries are located via this variable.
- export LD_LIBRARY_PATH="$(dos_to_msys_path $LD_LIBRARY_PATH):$(dos_to_msys_path $BINDIR)"
+if [ "$OS" == "Windows_NT" ]; then
+ export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
fi
##############
# 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="$(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="$BINDIR:$FEISTY_MEOW_GENERATED:$PATH:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/lib:/usr/games:/usr/bin:."
##############
projects / feisty_meow.git / blobdiff