[Glass] tode / pharo errors

[Jon Paynter via Glass]

yeah it seems knowing too much is getting in the way. I keep wanting to
start netldi and then stone, and stop them in reverse order.

but in order to use ssh port forwarding for tode, you will need a way to
specify the netldi port number on the startStone cmd, so for now I have to
use this:
./shared/downloads/products/GemStone64Bit3.2.8-x86_64.Linux/bin/startnetldi
-a gemstone -g -P 55278 seaside_ldi

So - on the VM here at work, the tode project list is functional and im
trying to create a new/blank project and add stuff.  According to the
"project entry" man page, II should be able to run this:
       project entry --git=builderGame --repo=$GS_HOME /home/external

And create a new project. but when I put that in the tode shell, i get an
error:
Topez ERROR: a TodeCommandError occurred (error 121000), Unknown option: git

Is the git option not finished? or is it that it cant find git on the host?
I know a few of the basic git commands, but virtually nothing about
MetaCello and how to use it.

Or would it be better to create a blank project by creating stuff in the
file system somehow?





On Wed, Oct 21, 2015 at 3:08 PM, Dale Henrichs <
dale.henrichs at gemtalksystems.com> wrote:

>
>
> On 10/21/2015 02:16 PM, Jon Paynter wrote:
>
>> Ok. so I went down the wrong road here...
>>
>> If putting everything under GsDevKit_home is preferred, then i will use
>> that (as I stated above, there is no old data that needs saving).  I was
>> under the (false) impression /op/gemstone and GsDevKit shared files.
>>
>> So to avoid future confusion, I removed /opt/gemstone from my VM, and
>> re-ran the installServer from a fresh clone.  I also had to update my
>> profile to remove references to /opt/gemstone
>>
>> The stone seems to be running according to the 'stones' command.
>>
>> next I need to start netldi with the correct port, so I stopped the
>> stone, but I cannot get the stopNetldi to work:
>> ...finished stopStone
>> gemstone at ubuntu:~/GsDevKit_home$ stopNetldi seaside_ldi
>>
> okay you stop a netldi by using the name of the stone ... the stone knows
> the name of the netldi that it is associated with (via the TDSession).
>
> You can use the -b option on the startStone and stopStone commands to stop
> both the stone and the netldi ...
>
>> =================
>>    GsDevKit script: stopNetldi seaside_ldi
>>               path: /home/gemstone/GsDevKit_home/bin/stopNetldi
>> =================
>> stopping netldi seaside_ldi
>> $GEMSTONE environment not set correctly
>>
>>
>> It looks like I missed a step somewhere to set the $GEMSTONE var.  what
>> should it be set to?
>>
> I should have a better error here when the stone is not found .... that
> may have helped you recognize ... I do recommend that you use the -h option
> to review the commandline arguments and options for the various commands
> ... I know that the GemStone stopnetldi command takes the name of the
> netldi and can lead to confusion when you "know too much:)"
>
> Dale
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20151022/b453102c/attachment.html>