it seems like we should no longer automatically check in feisty meow for all users, since most will hopefully have it installed system-wide, where users cannot update any files. additionally, most users don't have write permission anyway. since we really want to move towards a more distribution oriented approach, it seems better to take feisty_meow off the repository list. users who want it automatically updated from and/or checked in to git can add it back in their custom versions.
# 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="$(basename $FEISTY_MEOW_APEX) "
+#old: define_yeti_variable REPOSITORY_LIST="$(basename $FEISTY_MEOW_APEX) "
+ define_yeti_variable REPOSITORY_LIST=
# initializes the feisty meow build variables, if possible.
function initialize_build_variables()
# add a bunch of folders to the list for checkin & checkout. these are
# definitely personal, and some of them are fairly dated (the yeti and
# hoople folders, for example).
- REPOSITORY_LIST+="cloud ebooks web active/webwork"
+ REPOSITORY_LIST+="$(basename $FEISTY_MEOW_APEX) cloud ebooks web active/webwork"
# point to our local certificate for ssh usage.
export SVN_SSH="ssh -i $HOME/.ssh/id_dsa_sourceforge"