break out stone dir creation as separate script/step (feedback from Mariano) about gsdevkithome

[dalehenrich]

Yes. In MINE scripts, the following is expected: all stones are in a root folder, say, /whatever/sites/StoneX/gemstone/stoneStructureHere.

Then, all my scripts expect a stone name. Then, what I do at the very beginning of the script is source /whatever/sites/$1/gemstone/stone.env

However....it would be very easy to change the scripts and they check if the argument $1 is a stone name (not starting with /), or a full path. Then you can send just stone name, and hence search it in "default" location or if desired, send full path.
So...I would do that as a first step.

Of course, a second step which is also easy, is to define a $STONES_DIRECTORIES and let the user export that var as desired. Then the scripts would check, if it is a stone name, then search iterating in $STONES_DIRECTORIES. If it is full path, they source directly.

I wanted to do that for my scripts but since I don't need it, I didn't do it yet.