superDoit project should be an isolated git checkout in GsDevKit_home to eliminate the need to copy files between two projects

[dalehenrich]

in the last several months @JupiterJones, @jbrichau, and I have been working on using superDoit technology and topaz solo extents to replace the 32 bit Pharo image used in many of the bash commands in the tool kit. We have plans plans to completely replace the bash scripts with superDoit scripts as well, but that is not our immediate goal.

Up until now, we have housed the superDoit artifacts in a superDoit_devkit directory. Over time the directory structure in the superDoit_devkit directory has diverged from the directory structure of the superDoit project itself. We rely on copying some of the common artifacts back and forth between varrious directoried inGsDevKit_home/superDoit_devkit and superDoit itself ... this is at best error prone, so I think in the best solution would be to "embed" a superDoit checkout in GsDevKit_home .. the only copy we will need to maintain is between the tonel (used by Rowan) and filetree (needed by tODE) packages directories and if push comes to shove, we could settle on using filetree so that no copying at all would be needed ...

• filetree and tonel format packages need to be support
  • separate tonel and filetree package dirs
  • .solo script for copying back and forth to keep both sets of packages in sync
  • separate specs for each
• may be prudent to just use filetree format packages at this point? GsDevKit/T2F2T-Conversion project makes copying between tonel and filetree pretty easy
• separate GsDevKit project(?) for shared GsDevKit code
• separate bin directory for _home scripts
• separate tode directory for tode filesystem bootstrap files (support for GsDevKit project)

[dalehenrich]

Now that I've got .stone scripts working (see dalehenrich/superDoit#10) I will get serious about integrating my work into GsDevKit_home ...

Instead of embedding a clone of superDoit, I think it make more sense to embed a copy of the superDoit working directory that way the scripts included in GsDevKit_home will always be assured to work with the embedded version of superDoit even if superDoit itself changes it's api over time ...

This looks like the expressions we would use to update superDoit in place with a new clone (from):

rm -rf superdoit_devkit
mkdir  superdoit_devkit
git clone --depth=1 --branch=master git@github.com:dalehenrich/superDoit.git superdoit_devkit
rm -rf ./superdoit_devkit/.git