# environment.
# Author: Chris Koeritz
+##############
+
+#hmmm: moved from functions.sh; does that hose everything up?
+
+ # defines a variable within the feisty meow environment and remembers that
+ # this is a new or modified definition. if the feisty meow codebase is
+ # unloaded, then so are all the variables that were defined.
+ # this function always exports the variables it defines.
+ function define_yeti_variable()
+ {
+# if variable exists already, save old value for restore,
+# otherwise save null value for restore,
+# have to handle unsetting if there was no prior value of one
+# we newly defined.
+# add variable name to a list of feisty defined variables.
+
+#hmmm: first implem just sets it up and exports the variable.
+# i.e., this method always exports.
+export "${@}"
+
+
+return 0
+ }
+
+
##############
# this section should always run or bash will reset them on us.
# these need to be as minimal as possible.
# sets the main prompt to a simple default, with user@host.
-export PS1='\u@\h $ ';
+define_yeti_variable PS1='\u@\h $ ';
# sets the history length and max file size so we can get some long history around here.
-export HISTSIZE=1000000
-export HISTFILESIZE=8000000
+define_yeti_variable HISTSIZE=1000000
+define_yeti_variable HISTFILESIZE=8000000
+
+# make the TERM available to all sub-shells.
+define_yeti_variable TERM
##############
# 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
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo variables initialization begins...; fi
##############
# start with some simpler things.
- export SCRIPT_SYSTEM=feisty_meow
+ define_yeti_variable SCRIPT_SYSTEM=feisty_meow
# OS variable records the operating system we think we found.
if [ -z "$OS" ]; then
- export OS=UNIX
+ define_yeti_variable OS=UNIX
fi
- export IS_DARWIN=$(echo $OSTYPE | grep -i darwin)
+ define_yeti_variable IS_DARWIN=$(echo $OSTYPE | grep -i darwin)
##############
# IS_MSYS will be non-empty if this is the msys toolset. otherwise
# we assume that it's cygwin.
IS_MSYS=$(uname | grep -i ming)
+
+ # if not MSYS, then we'll assume cygwin and set the cygwin root var.
+ if [ -z "$IS_MSYS" ]; then
+ define_yeti_variable CYGROOT=$(cygpath -w -m /)
+ fi
fi
##############
# 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 [ -z "$FEISTY_MEOW_APEX" ]; then
if [ -d "$HOME/feisty_meow" ]; then
- export FEISTY_MEOW_DIR="$HOME/feisty_meow"
- export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_SCRIPTS"
+ define_yeti_variable FEISTY_MEOW_APEX="$HOME/feisty_meow"
+ define_yeti_variable FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_SCRIPTS"
fi
fi
-
+
+ # main declaration of the transients area.
+ if [ -z "$TMP" ]; then
+ define_yeti_variable TMP=$HOME/.tmp
+ fi
+
+ # set up the top-level for all build creations and logs and such.
+ if [ -z "$FEISTY_MEOW_GENERATED_STORE" ]; then
+ define_yeti_variable FEISTY_MEOW_GENERATED_STORE="$TMP/generated-feisty_meow"
+ fi
+ if [ ! -d "$FEISTY_MEOW_GENERATED_STORE" ]; then
+ mkdir -p "$FEISTY_MEOW_GENERATED_STORE"
+ fi
+ # set up our effluent outsourcing valves.
+ if [ -z "$TEMPORARIES_PILE" ]; then
+ define_yeti_variable TEMPORARIES_PILE="$FEISTY_MEOW_GENERATED_STORE/temporaries"
+ fi
+ if [ ! -d "$TEMPORARIES_PILE" ]; then
+ mkdir -p "$TEMPORARIES_PILE"
+ fi
+
# 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
+ if [ -z "$FEISTY_MEOW_LOADING_DOCK" ]; 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
+ define_yeti_variable FEISTY_MEOW_LOADING_DOCK=$HOME/.zz_feisty_loading
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. the mask used here
- # disallows writes by the "group" and disallows "others" completely.
- umask 027
+ ##############
+
+ # umask sets a permission mask for all file creations.
+ # this mask disallows writes by "group" and "others".
+ umask 022
+ # this mask disallows writes by the "group" and disallows "others" completely.
+ #umask 027
+
# 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.
# define a default name, if one wasn't already set.
if [ -z "$NAME" ]; then
- export NAME='Unset Q. Namington, Fixley Your Name III'
+ define_yeti_variable 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
+ define_yeti_variable PERLLIB+="/usr/lib/perl5"
+ define_yeti_variable PERL5LIB+="/usr/lib/perl5"
+ if [ "$OS" == "Windows_NT" ]; then
+ define_yeti_variable 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
# 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"
+ PERLLIB+=":$(dos_to_unix_path $i)"
+ PERL5LIB+=":$(dos_to_unix_path $i)"
fi
fi
done
##############
# 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
+ 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"
+
# 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"
-
+ # names can be added in your customized scripts. the space at the end of
+ # this variable is important and allows users to extend the list like:
+ # define_yeti_variable REPOSITORY_DIR+="muppets configs"
+ # see the customize/fred folder for a live example.
+ define_yeti_variable REPOSITORY_LIST="$FEISTY_MEOW_APEX "
+
+ # the archive collections list is a set of directories that are major
+ # repositories of data which can be synched to backup drives.
+ define_yeti_variable ARCHIVE_COLLECTIONS_LIST=
+
# 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
+ if [ -z "$FEISTY_MEOW_APEX" ]; then return; fi
# pick from our expected generator folder, but make sure it's there...
buildvars="$FEISTY_MEOW_SCRIPTS/generator/build_variables.sh"
if [ -f "$buildvars" ]; then
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. we set
- # up the path to it here based on the operating system.
- export BINDIR=$FEISTY_MEOW_DIR/production/binaries
+ # the binary directory contains our collection of handy programs.
+ define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_STORE
# add binaries created within build to the path.
- export PATH="$BINDIR:$PATH"
+ define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_BINARIES):$PATH"
# Shared libraries are located via this variable.
- export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$BINDIR"
+ define_yeti_variable LD_LIBRARY_PATH="$(dos_to_unix_path $LD_LIBRARY_PATH):$(dos_to_unix_path $FEISTY_MEOW_BINARIES)"
fi
}
# windoze specific patching up missing things.
if [ "$OS" == "Windows_NT" ]; then
- export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
+ define_yeti_variable HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
fi
##############
# add to the PATH variables used for locating applications. this step is taken after any
# potential overrides from the user.
- export PATH="$FEISTY_MEOW_GENERATED:$PATH:$(find /usr/local/games -maxdepth 1 -type d -exec echo -n {}: ';' 2>/dev/null)/sbin"
+ define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_LOADING_DOCK):$PATH:$(find /usr/local/games -maxdepth 1 -type d -exec echo -n {}: ';' 2>/dev/null)/sbin"
##############
- # set the SHUNIT_DIR so our shunit tests can find the codebase.
- export 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"
##############
-
- if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi
+ define_yeti_variable CORE_VARIABLES_LOADED=true
+
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo variables initialization ends....; fi
fi
##############
# override individual variables and definitions. we also don't guard this
# to avoid running it again, because we don't know what mix of functions and
# aliases they want to define in there.
-for i in $FEISTY_MEOW_GENERATED/custom/*.sh; do
+for i in $FEISTY_MEOW_LOADING_DOCK/custom/*.sh; do
if [ ! -f "$i" ]; then
# skip it if it's not real.
continue;
fi
- if [ ! -z "$SHELL_DEBUG" ]; then
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then
echo "loading customization: $(basename $(dirname $i))/$(basename $i)"
fi
- source $i
+ source "$i"
done
-
+