updated to get closer to building using cygwin, which is difficult because

[feisty_meow.git] / scripts / core / bootstrap_shells.sh

diff --git a/scripts/core/bootstrap_shells.sh b/scripts/core/bootstrap_shells.sh
index c8e4a3cda83a42952a89a40657f9e13b22fb91ff..0f7ad4a68bf4910d0a1c1b98550716fa0619e764 100644 (file)
--- a/scripts/core/bootstrap_shells.sh
+++ b/scripts/core/bootstrap_shells.sh
@@ -3,56 +3,53 @@
 # bootstrap_shells:
 #
 # This script creates the directory for auto-generated scripts and gets
-# the current user's account ready to use YETI.
+# the current user's account ready to use the feisty meow scripts.
 #
-# Note: this does not yet ensure that the YETI profile is executed on
-# shell startup.  that can be added manually by editing your .bashrc file.
-# read the examples/bashrc_user file for more details.
+# Note: this does not yet ensure that the profile is executed on shell
+# startup.  that can be added manually by editing your .bashrc file.
+# read the examples/feisty_meow_startup/bashrc_user file for more details.
 
 ORIGINATING_FOLDER="$( \cd "$(\dirname "$0")" && \pwd )"
-YETI_CORE_SCRIPTS_DIR="$(echo "$ORIGINATING_FOLDER" | tr '\\\\' '/' )"
+CORE_SCRIPTS_DIR="$(echo "$ORIGINATING_FOLDER" | tr '\\\\' '/' )"
 THIS_TOOL_NAME="$(basename "$0")"
 
-## check this scripts directory; do we find this script there?
-#pushd "/" &>/dev/null  # jump to root so relative paths have to fail.
-#if [ ! -f "$YETI_CORE_SCRIPTS_DIR/$THIS_TOOL_NAME" ]; then
-#  echo "This script must be run using its full pathname.  This enables the script to"
-#  echo "locate the proper folders.  Please try again with the full path, e.g.:"
-#  echo "    bash /home/fred/codeplex/$THIS_TOOL_NAME"
-#  exit 1
-#fi
-#popd &>/dev/null
-
-# set up the yeti dir.
-pushd "$YETI_CORE_SCRIPTS_DIR/../.." &>/dev/null
-export YETI_DIR="$(pwd)"
+# set up the feisty_meow dir.
+pushd "$CORE_SCRIPTS_DIR/../.." &>/dev/null
+source "$CORE_SCRIPTS_DIR/functions.sh"
+export FEISTY_MEOW_DIR="$(pwd)"
 popd &>/dev/null
-#echo yeti is $YETI_DIR
 
-export YETI_SCRIPTS="$YETI_DIR/scripts"
-export SHELLDIR="$YETI_SCRIPTS"
+export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_DIR/scripts"
 
-# GENERADIR is where the generated files yeti uses are located.
-export GENERADIR="$HOME/.zz_auto_gen"
-if [ ! -z "$WINDIR" -o ! -z "$windir" ]; then
-  # assume they are using windoze.
-  export GENERADIR="$TMP/zz_auto_gen"
+# FEISTY_MEOW_GENERATED is where the generated files feisty_meow uses are located.
+export FEISTY_MEOW_GENERATED="$HOME/.zz_auto_gen"
+if [ ! -d "$FEISTY_MEOW_GENERATED" ]; then
+  mkdir "$FEISTY_MEOW_GENERATED"
 fi
-if [ ! -d "$GENERADIR" ]; then
-  mkdir "$GENERADIR"
+# make toast out of generated files right away, but leave any custom scripts.
+find "$FEISTY_MEOW_GENERATED" -maxdepth 1 -type f -exec rm -f "{}" ';' &>/dev/null
+if [ ! -d "$FEISTY_MEOW_GENERATED/custom" ]; then
+  mkdir "$FEISTY_MEOW_GENERATED/custom"
 fi
 
-YETIVARS="$GENERADIR/yeti_variables.sh"
-echo >"$YETIVARS"
-for i in YETI_DIR YETI_SCRIPTS SHELLDIR GENERADIR; do
-  echo "export $i=${!i}" >>"$YETIVARS"
+# just a variable we use in here to refer to the generated variables file.
+GENERATED_FEISTY_MEOW_VARIABLES="$FEISTY_MEOW_GENERATED/fmc_variables.sh"
+# create the alias file as totally blank.
+echo -n >"$GENERATED_FEISTY_MEOW_VARIABLES"
+for i in FEISTY_MEOW_DIR FEISTY_MEOW_SCRIPTS FEISTY_MEOW_GENERATED; do
+  echo "export $i=${!i}" >>"$GENERATED_FEISTY_MEOW_VARIABLES"
 done
 
+# load our variables so we get a useful PERLLIB variable.
+source "$FEISTY_MEOW_SCRIPTS/core/variables.sh"
+
 # create our common aliases.
-perl "$YETI_SCRIPTS/core/generate_aliases.pl"
+perl "$FEISTY_MEOW_SCRIPTS/core/generate_aliases.pl"
 
-echo -e '\n\n'
-echo Established this set of variables to describe how to find yeti assets:
-cat "$YETIVARS"
-echo -e '\n'
+if [ ! -z "$SHELL_DEBUG" ]; then
+  echo established these variables for feisty_meow assets:
+  echo ==============
+  cat "$GENERATED_FEISTY_MEOW_VARIABLES"
+  echo ==============
+fi