##############
-#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,
+ #hmmm: simple implem just sets it up and exports the variable.
+ # i.e., this method always exports.
+ export "${@}"
+
+#hmmm: eventual approach-- 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
}
+ # switches from an X:/ form to a /cygdrive/X/path form. this is only useful
+ # for the cygwin environment currently.
+ # defined here rather than in functions.sh since we need it when setting variables
+ # and cannot count on load order during a fresh startup in some circumstances.
+ function dos_to_unix_path() {
+ # we always remove dos slashes in favor of forward slashes.
+#old: echo "$1" | sed -e 's/\\/\//g' | sed -e 's/\([a-zA-Z]\):\/\(.*\)/\/\1\/\2/'
+ echo "$1" | sed -e 's/\\/\//g' | sed -e 's/\([a-zA-Z]\):\/\(.*\)/\/cygdrive\/\1\/\2/'
+ }
+
+
##############
# we'll run this again only if we think it's needed.
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.
+#hmmm: this needs to come from some configuration item. especially for installs.
+define_yeti_variable DEFAULT_FEISTYMEOW_ORG_DIR=/opt/feistymeow.org
+
define_yeti_variable SCRIPT_SYSTEM=feisty_meow
# OS variable records the operating system we think we found.
# this is only used for extreme failure modes, when the values were not
# pulled in from our auto-generated config.
if [ -z "$FEISTY_MEOW_APEX" ]; then
- if [ -d "$HOME/feisty_meow" ]; then
+ if [ -d "/opt/feistymeow.org/feisty_meow" ]; then
+ define_yeti_variable FEISTY_MEOW_APEX="/opt/feistymeow.org/feisty_meow"
+ define_yeti_variable FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_APEX/scripts"
+ elif [ -d "$HOME/feisty_meow" ]; then
define_yeti_variable FEISTY_MEOW_APEX="$HOME/feisty_meow"
- define_yeti_variable FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_SCRIPTS"
+ define_yeti_variable FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_APEX/scripts"
fi
fi
define_yeti_variable TMP=$HOME/.tmp
fi
+ # set up our event logging file for any notable situation to be recorded in.
+ if [ -z "$FEISTY_MEOW_EVENT_LOG" ]; then
+ define_yeti_variable FEISTY_MEOW_EVENT_LOG="$TMP/$USER-feisty_meow-events.log"
+ fi
+
# set up the top-level for all build creations and logs and such.
- if [ -z "$GENERATED_DIR" ]; then
- define_yeti_variable GENERATED_DIR="$TMP/generated-feisty_meow"
+ if [ -z "$FEISTY_MEOW_GENERATED_STORE" ]; then
+ define_yeti_variable FEISTY_MEOW_GENERATED_STORE="$TMP/generated-feisty_meow"
fi
- if [ ! -d "$GENERATED_DIR" ]; then
- mkdir -p "$GENERATED_DIR"
+ if [ ! -d "$FEISTY_MEOW_GENERATED_STORE" ]; then
+ mkdir -p "$FEISTY_MEOW_GENERATED_STORE"
fi
# set up our effluent outsourcing valves.
- if [ -z "$TEMPORARIES_DIR" ]; then
- define_yeti_variable TEMPORARIES_DIR="$GENERATED_DIR/temporaries"
- fi
- if [ ! -d "$TEMPORARIES_DIR" ]; then
- mkdir -p "$TEMPORARIES_DIR"
+ define_yeti_variable TEMPORARIES_PILE="$FEISTY_MEOW_GENERATED_STORE/temporaries"
+ if [ ! -d "$TEMPORARIES_PILE" ]; then
+ mkdir -p "$TEMPORARIES_PILE"
fi
# similarly, make sure we have someplace to look for our generated files, if
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.
- # this mask disallows writes by "group" and "others".
- umask 022
- # this mask disallows writes by the "group" and disallows "others" completely.
+ ##############
+
+ # umask sets a permission mask for all file creations. we don't set this for the users any
+ # more; they should set it themselves. this is just documentation.
+ #
+ # this mask disallows writes by the "group" and disallows all permissions for "others".
#umask 027
+ # this mask disallows writes by "group" and "others".
+ #umask 022
+ # this mask allows writes by "group" but not by "others".
+ #umask 002
# 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
# variables for perl.
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
ls $i/*.pl &>/dev/null
if [ $? -eq 0 ]; then
PERLLIB+=":$(dos_to_unix_path $i)"
- PERL5LIB+=":$(dos_to_unix_path $i)"
fi
fi
done
+ define_yeti_variable PERL5LIB=$PERLLIB
#echo PERLLIB is now $PERLLIB
##############
# set this so nechung can find its data.
define_yeti_variable NECHUNG=$FEISTY_MEOW_APEX/infobase/fortunes.dat
- # ensure we use the right kind of secure shell.
-# define_yeti_variable CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
-# define_yeti_variable GIT_SSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
-
+## # 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. 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"
- define_yeti_variable REPOSITORY_LIST="feisty_meow "
+ # see the customize/fred folder for a live example.
+ define_yeti_variable REPOSITORY_LIST="$FEISTY_MEOW_APEX "
+
+ # add in any active projects to the repository list.
+ if [ -d "$HOME/active" ]; then
+ REPOSITORY_LIST+="$(find "$HOME/active" -maxdepth 1 -mindepth 1 -type d) "
+ fi
+ # add in any site avenger applications that are in the applications folder.
+ if [ -d "$HOME/apps" ]; then
+ # general search for normal project folders in apps.
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname ".git" -type d -exec dirname {} ';') "
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname ".svn" -type d -exec dirname {} ';') "
+
+ # special search for site avenger directories; they have avenger5 as second level.
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname "avenger5" -type d) "
+ fi
+ # the archive list is a set of directories that are major repositories of
+ # data which can be synched to backup drives.
+ define_yeti_variable MAJOR_ARCHIVE_SOURCES=
+ # the source collections list is a set of directories that indicate they
+ # harbor a lot of source code underneath.
+ define_yeti_variable SOURCECODE_HIERARCHY_LIST=
+
# initializes the feisty meow build variables, if possible.
function initialize_build_variables()
{
# now augment the environment if we found our build variables.
if [ $found_build_vars == 1 ]; then
# the binary directory contains our collection of handy programs.
- define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_DIR
+ define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_STORE
# add binaries created within build to the path.
define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_BINARIES):$PATH"
# Shared libraries are located via this variable.
# add to the PATH variables used for locating applications. this step is taken after any
# potential overrides from the user.
- 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"
+#old: 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"
+ define_yeti_variable PATH="$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.
- define_yeti_variable 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"
##############
define_yeti_variable CORE_VARIABLES_LOADED=true
- if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo variables initialization ends....; fi
fi
##############
-# pull in the custom overrides for feisty_meow scripts. this is done last,
-# because we want to set everything up as expected, then let the user
+# pull in the custom overrides for feisty_meow scripts. this is done almost
+# last, because we want to set everything up as expected, then let the user
# 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.
# 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"
done
+##############
+
+# a late breaking action is to set the editor, if we can.
+# we will fallback to whatever we can find on the host.
+export EDITOR
+# note: the editors for revision control must wait while the document is
+# edited, so gvim and others that launch a separate x window are not
+# going to work well unless they can be prevented from forking the process
+# off.
+if [ -z "$EDITOR" ]; then
+ EDITOR="$(which gvim)"
+ if [ ! -z "$EDITOR" ]; then
+ # if we found gvim, then add in the no forking flag.
+ EDITOR+=" --nofork"
+ fi
+fi
+if [ -z "$EDITOR" ]; then
+ EDITOR="$(which vim)"
+fi
+if [ -z "$EDITOR" ]; then
+ EDITOR="$(which vi)"
+fi
+if [ -z "$EDITOR" ]; then
+ EDITOR="$(which emacs)"
+fi
+####
+# out of ideas about editors at this point.
+####
+# set the VISUAL and other variables from EDITOR if we found an editor to use.
+if [ ! -z "$EDITOR" ]; then
+ VISUAL="$EDITOR"
+
+ export GIT_EDITOR="$EDITOR"
+ export SVN_EDITOR="$EDITOR"
+fi
+
+##############
+
projects / feisty_meow.git / blobdiff