working towards using a script launcher to clean things up
adding a handy message to indicate that the script has died
on error initiated exit, print the message as 'error'
breaking out the repository update so it can be called independently of the 'restart the whole of starphleet' business as well as making the repository relative to the git repo from which it's run, which will need to be changed... but hey... you can't have everything all at once
switching branch
simplification
trying to come up with the simplest possible way to handle the may/may not have local starphleet repo
adding starphleet-local-repo-update
adding some helper methods around changing directories
this must be run from a sibling directory of the overlay directory (i.e. within a clone of the starphleet repo)
oops, sibling directory
fixed invalid spelling of silent_p*
adding a handy indicator of where the local repository that was updated is
trying for a working version of patch
switching to start / stop metaphor from restart as, per the docs, restart doesn't pick up new job configurations which is the whole point of patching
silent directory changes
Phil's changes exposed the fact that the lib64z1-dev package is not available to the Ubuntu AMI based EC2 images, it's simply not in their package repository.  The changes caused this to break the install, but previously the failed install was simply skipped ( and none of the Ubuntu based EC2 images have this available ).  Sine the other ships are running fine without this package being installed, and it now causes the install to fail, I'm removing it
Merge remote-tracking branch 'origin/master' into refactory
adding a open file descriptor limit that is large
Merge remote-tracking branch 'origin/refactory' into multibeta