cleaned out yeti phrasings.

diff --git a/scripts/core/bootstrap_shells.sh b/scripts/core/bootstrap_shells.sh
index 7dba79d4315ace93653a6eb923cbc001bafcfc59..a4031bcaf37bb5176674de6da9727a69f456c1dd 100644 (file)
--- a/scripts/core/bootstrap_shells.sh
+++ b/scripts/core/bootstrap_shells.sh
@@ -3,18 +3,18 @@
 # 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.
+# 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")"
 
 # set up the feisty_meow dir.
-pushd "$YETI_CORE_SCRIPTS_DIR/../.." &>/dev/null
+pushd "$CORE_SCRIPTS_DIR/../.." &>/dev/null
 export FEISTY_MEOW_DIR="$(pwd)"
 popd &>/dev/null
 

diff --git a/scripts/core/generate_aliases.pl b/scripts/core/generate_aliases.pl
index 660fdd8d5a1b8a042647bf902af0e1b61b9a5f0d..ead37dac32e51d21dd2f10c8e3f7acd1044280ad 100644 (file)
--- a/scripts/core/generate_aliases.pl
+++ b/scripts/core/generate_aliases.pl
@@ -8,10 +8,10 @@
 #
 #  Purpose:
 #
-#    This script generates YETI alias files.  Alias files contain a list of
-#  definitions for command aliases that are written in the specified shell
-#  dialect (such as bash or perl) and which are additionally tailored for the
-#  operating system to be used.
+#    This script generates feisty meow script alias files.  Alias files
+#  contain a list of definitions for command aliases that are written in the
+#  specified shell dialect (such as bash or perl) and which are additionally
+#  tailored for the operating system to be used.
 #
 ##############
 #  This program is free software; you can redistribute it and/or modify it
@@ -155,7 +155,7 @@ if ( ! length("$FEISTY_MEOW_GENERATED") ) {
 The FEISTY_MEOW_GENERATED variable is not defined.  This must point to the location where\n\
 the generated scripts are stored.  Perhaps you still need to run\n\
 bootstrap_shells.sh and set up some environment variables.  Please see\n\
-http://yeticode.org for more details.\n";
+http://feistymeow.org for more details.\n";
   exit 1;
 #really need to use better exit codes.
 }
@@ -171,7 +171,7 @@ if (! -d $FEISTY_MEOW_GENERATED) {
 
 ##############
 
-# set the executable bit for yeti binaries for just this current user.
+# set the executable bit for binaries for just this current user.
 if (-d $BINDIR) {
   system("chmod -R u+x \"$BINDIR\"/*");
 }
@@ -195,7 +195,7 @@ open(she, ">> $FEISTY_MEOW_GENERATED/fmc_aliases_for_scripts.sh");
 # find the list of files in the scripts directory.
 #opendir(scripts, "$FEISTY_MEOW_SCRIPTS");
 #@shell_files = sort(readdir(scripts));
-#print "yeti scripts: @shell_files\n";
+#print "scripts: @shell_files\n";
 
 @shell_files = &load_file_names("$FEISTY_MEOW_SCRIPTS");
 

diff --git a/scripts/core/launch_feisty_meow.sh b/scripts/core/launch_feisty_meow.sh
index 38c304c0eff468655ded620a980695feea872b6c..fa9d34e822ee954350bd9c6c98fffdf227c0bb68 100644 (file)
--- a/scripts/core/launch_feisty_meow.sh
+++ b/scripts/core/launch_feisty_meow.sh
@@ -20,7 +20,7 @@ export ERROR_OCCURRED=
 ##############
 
 if [ -z "$FEISTY_MEOW_GENERATED" ]; then
-  # FEISTY_MEOW_GENERATED is where the generated files yeti uses are located.
+  # FEISTY_MEOW_GENERATED is where the generated files are located.
   # this is our single entry point we can use without knowing any variables
   # yet in the initialization process.
   export FEISTY_MEOW_GENERATED="$HOME/.zz_auto_gen"
@@ -30,7 +30,7 @@ if [ -z "$FEISTY_MEOW_GENERATED" ]; then
   GENERATED_FEISTY_MEOW_VARIABLES="$FEISTY_MEOW_GENERATED/fmc_variables.sh"
   if [ ! -f "$GENERATED_FEISTY_MEOW_VARIABLES" ]; then
     echo -e '\n\n'
-    echo "The yeti scripts need to be initialized via the bootstrap process, e.g.:"
+    echo "Feisty meow scripts need initialization via the bootstrap process, e.g.:"
     echo "  bash $HOME/feisty_meow/scripts/core/bootstrap_shells.sh"
     echo -e '\n\n'
     ERROR_OCCURRED=true

diff --git a/scripts/core/variables.sh b/scripts/core/variables.sh
index 3f36b21f1ade30f0b66e23e44e2b17d1cf2228e2..f40dfc4f81dc76486b5f320fb4b7bb030e33ac28 100644 (file)
--- a/scripts/core/variables.sh
+++ b/scripts/core/variables.sh
@@ -134,20 +134,12 @@ if [ -z "$NECHUNG" ]; 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 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.
+      # 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
-  
       # 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
   }