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
# 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
# set this so nechung can find its data.
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"
+## # establish a pipe for less to see our beloved syntax highlighting.
+## define_yeti_variable LESSOPEN="| source-highlight -f esc -o STDOUT -i %s"
# ensure we use the right kind of secure shell.
# define_yeti_variable CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
# 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=
+ # 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()
{