6 # Defines the environment variables used by the personalized unix
8 # Author: Chris Koeritz
12 if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization begins...; fi
16 # start with some simpler things.
18 export SCRIPT_SYSTEM=feisty_meow
20 # OS variable records the operating system we think we found.
24 export IS_DARWIN=$(echo $OSTYPE | grep -i darwin)
28 # windoze sometimes needs a special home variable setup.
29 if [ "$OS" == "Windows_NT" ]; then
30 # give them a default place if they don't have one already.
31 if [ -z "$HOME" ]; then
34 # patch home to undo cygwin style of drive letter.
35 export HOME=$(echo $HOME | sed -e 's/\/cygdrive\//\//g')
36 # make the home folder if it doesn't exist yet.
37 if [ ! -d $HOME ]; then
40 if [ ! -z "$SHELL_DEBUG" ]; then echo HOME is now $HOME; fi
45 # fallbacks to set crucial variables for feisty meow...
47 # set the main root directory variable for the feisty meow codebase.
48 # this is only used for extreme failure modes, when the values were not
49 # pulled in from our auto-generated config.
50 if [ -z "$FEISTY_MEOW_DIR" ]; then
51 if [ -d "$HOME/feisty_meow" ]; then
52 export FEISTY_MEOW_DIR="$HOME/feisty_meow"
53 export FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_DIR/scripts"
57 # similarly, make sure we have someplace to look for our generated files, if
58 # we were not handed a value.
59 if [ -z "$FEISTY_MEOW_GENERATED" ]; then
60 # The generated scripts directory is where automatically generated files live.
61 # It is separate from the main body of the shell scripts in order to keep things from
63 export FEISTY_MEOW_GENERATED=$HOME/.zz_auto_gen
68 # umask sets a permission mask for all file creations. the mask used here
69 # disallows writing by the "group" and "others" categories.
71 # ulimit sets user limits. we set the maximum allowed core dump file size
72 # to zero, because it is obnoxious to see the core dumps from crashed
73 # programs lying around everywhere.
78 # include helpful functions.
79 source "$FEISTY_MEOW_SCRIPTS/core/functions.sh"
83 # user variables, sort of... if they haven't given themselves a name yet,
84 # then we will make one up for them.
86 # define a default name, if one wasn't already set.
87 if [ -z "$NAME" ]; then
88 export NAME='Unset Q. Namington, Fixley Your Name III'
93 # sets the main prompt to a simple default, with user@host.
94 export PS1='\u@\h $ ';
101 if [ "$OS" != "Windows_NT" ]; then
102 PERLLIB+="/usr/lib/perl5"
104 export PERLIO=:perlio
105 # choose perl's IO over the ms-windows version so we can handle file
109 # iterate across our sub-directories and find the perl scripts.
110 # this currently only looks one level down.
111 for i in $FEISTY_MEOW_SCRIPTS/*; do
113 # check if there is a perl file present; add the folder to PERLLIB if so.
114 ls $i/*.pl &>/dev/null
115 if [ $? -eq 0 ]; then
120 #echo PERLLIB is now $PERLLIB
124 # set this so nechung can find its data.
125 export NECHUNG=$FEISTY_MEOW_DIR/database/fortunes.dat
127 # ensure we use the right kind of rsh for security.
130 # sets the history length and max file size so we can get some long history around here.
134 # the base checkout list is just to update feisty_meow. additional folder
135 # names can be added in your customized scripts.
136 export REPOSITORY_LIST="feisty_meow"
138 # set the editor for subversion if it hasn't already been set.
139 if [ -z "$SVN_EDITOR" ]; then
140 #hmmm: not sure what original reason for having these different was...
141 if [ "$OS" == "Windows_NT" ]; then
142 export SVN_EDITOR=$(which gvim)
144 export SVN_EDITOR=$(which vi)
148 # initializes the feisty meow build variables, if possible.
149 function initialize_build_variables()
152 # we need to know the feisty meow directory, or we bail.
153 if [ -z "$FEISTY_MEOW_DIR" ]; then return; fi
154 # pick from our expected generator folder, but make sure it's there...
155 buildvars="$FEISTY_MEOW_DIR/scripts/generator/build_variables.sh"
156 if [ -f "$buildvars" ]; then
157 # yep, that one looks good, so pull in the build defs.
158 source "$buildvars" "$buildvars"
161 # now augment the environment if we found our build variables.
162 if [ $found_build_vars == 1 ]; then
163 # the binary directory contains handy programs we use a lot in yeti. we set up the path to it
164 # here based on the operating system.
165 # note that yeti has recently become more dependent on hoople. hoople was always the source of
166 # the binaries, but now we don't ship them with yeti any more as pre-built items. this reduces
167 # the size of the code package a lot and shortens up our possible exposure to compromised
168 # binaries. people can bootstrap up their own set from hoople now instead.
169 export BINDIR=$FEISTY_MEOW_DIR/production/binaries
171 # add binaries created within build to the path.
172 export PATH="$(dos_to_msys_path $BUILD_TOP/build/bin):$PATH"
174 # Shared libraries are located via this variable.
175 export LD_LIBRARY_PATH="$(dos_to_msys_path $LD_LIBRARY_PATH):$(dos_to_msys_path $BINDIR)"
179 # load in the build environment.
180 initialize_build_variables
184 # windoze specific patching up missing things.
186 if [ "$OS" == "Windows_NT" ]; then
187 export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
192 # pull in the custom overrides for feisty_meow scripts. this is done last,
193 # because we want to set everything up as expected, then let the user
194 # override individual variables and definitions.
195 for i in $FEISTY_MEOW_GENERATED/custom/*.sh; do
196 if [ ! -f "$i" ]; then
197 # skip it if it's not real.
200 if [ ! -z "$SHELL_DEBUG" ]; then
201 echo "loading customization: $(basename $(dirname $i))/$(basename $i)"
208 # set the path for locating applications. this is done after any
209 # potential overrides from the user.
210 export PATH="$(dos_to_msys_path $BINDIR):$(dos_to_msys_path $FEISTY_MEOW_GENERATED):$PATH:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/lib:/usr/games:/usr/bin:."
214 if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi