support use of smalltalkCI smalltalk.ston files for loading tODE and creating non-tODE Pharo clients

[dalehenrich]

Both the gsDevKitCommandLineLoad.st and todeLoad.st scripts in $GS_HOME/sys/default/pharo could be replaced by a SmalltalkCI .smalltalk.ston file ...

This would also open the door for creating pharo client images for testing GsDevKit/GemStone-GCI projects on travis as well as creating prodution/development clients for projects like Tugrik or custom tODE clients for projects like Obex

[dalehenrich]

• STEP 1: let's teach ${GS_TODE_CLIENT}/bin/createPharoTodeClient to create a simple pharo image without loading tODE.

[dalehenrich]

• STEP 2: use SmalltalkCI smalltalk.ston file to create contents of image ... this means we need to add SmalltalkCI project to our list of supported git repos

[dalehenrich]

add SmalltalkCI project to list of supported git repos: 2a1f230...de82b61

[dalehenrich]

• STEP 3: Figure out how to:
  • create and start stone with project code loaded and run --- https://github.com/GsDevKit/GemStone-GCI is a good test case
  • create and start client with project code and tests loaded and run
  • work through the scenarios locally because this will likely require both smalltalkCI changes as well as additional GsDevKit+home support

symbolic link to last GemStone build?
symbolic like to pharo client?

[dalehenrich]

Regarding STEP 3 ... my current thoughts are to:

• modify SmalltalkCI and add the methods described here - see hpi-swa/smalltalkCI@1f0c9a1
• include SmalltalkCI in the devKitCommandLine image
• add support to the devKitCommandLine image for doing the smalltalkCI dirty work specifically:
  1. preparing the dependency cache and creating the stone in gemstone/run.sh prepare_stone()
  2. loading the project and running the tests in gemstone/run.sh load_and_test_project()
• add the new smalltalkCI classes described here
• then implement the create and start client with project code and tests loaded and run.

[dalehenrich]

It does not make sense to prepre the dependency cache using devKitCommandLine, because one of the files that is cached is the devKitCommandLine image ... ah well nice try ... we should be able to create the stone ...

[dalehenrich]

Will need to add script for createSmalltalkCIStone ... actually if I add the appropriate option to createStone (-i?) so that createSmalltalkCIStone devKitCommandLine command is called instead of createStone, we should be good to go ... if smalltalkCI env vars aren't present the default behavior is to do a standard createStone so it's pretty safe ...

[dalehenrich]

on other fronts, there is more work being done in the bash script itself than I anticipated ... I will need to change strategies here for the createStone logic ... the main reason for pulling things into pharo is that pharo will be able to understand the .smalltalk.ston file and a bash script will never be able to ... now that I'm here and poised for action letls look a bit more closely at exactly what needs to be done.

[dalehenrich]

With the previous commits, I am adding -z option to createStone command (and others as needed) ... the -z option will be universally used for defining the smalltalkCI.ston path

[dalehenrich]

add support for multiple clients --- complete