Issue #260: eliminate reliance on 32 bit devKitCommanLine image -- call for volunteers

I have made pretty good process in creating the infrastructure support
needed to start using a 3.5.0 topaz solo extent and gsdevkit_launcher
scripts to replace the use of the 32 bit Pharo devKitCommandLine
image[1], but I will need a couple of more days until things are ready
for folks to start developing the replacement scripts as I've got a
handful of tasks left to finish[2].

I know that when I have finished my infrastructure work, folks will not
be chomping at the the bit  to get started, however, I do want to have
folks who intend to contribute over the next several months to let me
know, so that I can make you a contributor to the `issue_260` team[3]
(you have to be a member to see what's at the end of the link:).

So if you intend to contribute, the best way to get started is to send
me mail with your github id and I'll invite you to the issue_260 team.

The reason I want you on the issue_260 team is so that you will be able
to assign yourself to an open (and unassigned) issue before you start
work on an issue ... in this way we can avoid duplication of effort ...

There is also a github facility for team discussions and as a member of
the team you will be able to contribute to/follow those discussions so
when you find yourself with some time you will know as much as anyone
else about what is going on:) This discussion facility is not public, so
you have be a member just to follow along ...

Anyway, I will be trying to carve up the project into small bit-sized,
independent pieces that should be doable in a day or two, so the
commitment to any one issue should be pretty manageable ... remember
that any time you contribute will save me time in the end and get us to
completion faster, so don't be shy about becoming a member of the team:)

Dale

[1] https://github.com/GsDevKit/GsDevKit_home/issues/260
[2] https://github.com/GsDevKit/GsDevKit_home/issues/261
[3] https://github.com/orgs/GsDevKit/teams/issue_260
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

I've finally gotten around to finishing up the initial work needed for
others to start contributing (when they have time) to converting
GsDevKit_home from depending upon a 32 bit Pharo-3.0 image to using a 64
bit topaz solo extent.

The readme[1] has instructions for updating your GsDevKit_home
installation to function as a development environment for developing and
testing gsdevkit_launcher scripts.

There is a prebuilt topaz solo extent as a resource associated with
v0.1.0 tag[2]. And the `$GS_HOME/alt_bin/bootstrap_launcher` bash script
creates a stone suitable for writing/editing new scripts as well as
producing updated topaz solo extents.

So, I'm basically ready when you are:)

If you've got the time and inclination to start working on working on
the new scripts, let me know and I will help you figure out a place to
start ...

Dale

[1]
https://github.com/GsDevKit/GsDevKit_home/tree/issue_260/shared/repos/GsDevKit_launcher#gsdevkit_launcher
[2] https://github.com/GsDevKit/GsDevKit_home/releases/tag/v0.10.0

On 10/21/19 9:57 AM, Dale Henrichs wrote: _______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hi Dale,
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hey Jupiter,

Thanks for taking this for a spin ... and glad that you're testing with a mac:)

embedded replies below ...

Hi Dale,

Just some notes from my setup:

$GS_HOME/alt_bin/bootstrap_launcher

=================

   GsDevKit script: bootstrap_launcher 

              path: /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher

=================

+ gsdevkit_launcher_version=v0.10.0

+ pushd /opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone

/opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone /opt/git/SmalltalkAustralia/GsDevKit_home

+ '[' '!' -d product ']'

+ pushd snapshots

/opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone/snapshots /opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone /opt/git/SmalltalkAustralia/GsDevKit_home

+ curl -L -O -s -S https://github.com/GsDevKit/GsDevKit_home/releases/download/v0.10.0/extent0.gsdevkit_launcher.dbf.zip

+ rm -rf extent0.gsdevkit_launcher.dbf

+ unzip -q extent0.gsdevkit_launcher.dbf.zip

+ popd

/opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone /opt/git/SmalltalkAustralia/GsDevKit_home

+ stoneName=gsdevkit_launcher_350

+ createStone -g gsdevkit_launcher_350 3.5.0

===============================================

== lot of output removed 

===============================================

startnetldi[Info]: GemStone version '3.5.0'

startnetldi[Info]: Server 'gsdevkit_launcher_350_ldi' is already running.

...finished :: startNetldi gsdevkit_launcher_350

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Common/ChunkCompression.cpp:49: Error: unsupported compressor 8

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.200.3/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'

...finished :: createStone -g gsdevkit_launcher_350 3.5.0

+ /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/install_launcher.st --clone --populate=gsdevkit_launcher_350

env: gsdevkit_launcher: No such file or directory

++ error 47

++ local lineno=47

+++ basename /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher

++ exit_1_banner 'Error on or near line 47 :: bootstrap_launcher '

+++ basename /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher

++ printf '\033[91;1m%s :: bootstrap_launcher \033[0m\n' 'Error on or near line 47 :: bootstrap_launcher '

Error on or near line 47 :: bootstrap_launcher  :: bootstrap_launcher 

++ exit 1

puppy:GsDevKit_home jupiter$ 

Install_launcher.st exists as does the file it links to. I thought maybe the magic #!/usr/bin/env gsdevkit_launcher may be the issue since alt_path is not in the path until the next step of the install script.

So I added it to the path with:

. alt_bin/defHOME_PATH.env

Ah, good catch ... I probably had that set in the shell I was testing ..

Then I get the following:

...finished :: createStone -g gsdevkit_launcher_350 3.5.0

+ /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/install_launcher.st --clone --populate=gsdevkit_launcher_350

/opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/gsdevkit_launcher: line 36: realpath: command not found

mktemp: illegal option -- p

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...

       mktemp [-d] [-q] [-u] -t prefix 

/opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/gsdevkit_launcher: line 84: $vmScriptFile: ambiguous redirect

/opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone/product/bin/topaz: option -S requires an argument 

Usages:

 topaz -l [-I topaziniFile | -i] [-q] [-u useName] [-e configName]

        [-z configName] [-T tocSizeKB] [ -S scriptFile ] [-C configParams] [ -- additional args] 

 topaz [-r] [-I topaziniFile | -i] [-q] [-u useName] [ -X CaCertPaths ]

        [-n hostName:netldiName] [ -S scriptFile ] [ -- additional args]

 topaz -h|-v

  -C  <configParams>, takes precedence over params in config files;

        argument uses config file syntax.  requires -l .

  -e  specifies executable specific configuration file; requires -l .

  -h  print usage and exit.

  -i  ignore startup file .topazini

  -I  full path to initialization file, overrides default location for .topazini

  -l  use linked GCI library 

  -L  use linked GCI library and ignore 'set gemnet' in topaz initialization file

  -n hostName:netldiName for an X509 login; requires -r .

  -q  be quiet, no banner or other informational output.

  -r  use RPC GCI library (RPC is the default if neither -l nor -r).

  -T  specifies TOC size to use; takes precedence over GEM_TEMPOBJ_CACHE_SIZE from

       -C or config file(s); requires -l .

  -S  specifies a script file processed with INPUT, suppressing output until an error

  -u  sets default value of SET CACHENAME.

  -v  print version and exit.

  -X CaCertPaths for an X509 login, requires -r,

     must specify 3 paths in this order:

     -X 'stoneCA-dev.cert.pem;DataCurator.chain.pem;DataCurator.privkey.pem'

  -z  specifies system configuration file; requires -l .

  -- <additional args>  values after the -- are available as command line args in linked topaz. 

+ pushd /opt/git/SmalltalkAustralia/GsDevKit_home/server/stones/gsdevkit_launcher_350

/opt/git/SmalltalkAustralia/GsDevKit_home/server/stones/gsdevkit_launcher_350 /opt/git/SmalltalkAustralia/GsDevKit_home/shared/gemstone /opt/git/SmalltalkAustralia/GsDevKit_home

+ ./newBuild_SystemUser_gsdevkit_launcher_tode

/opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher: line 49: ./newBuild_SystemUser_gsdevkit_launcher_tode: No such file or directory

++ error 49

++ local lineno=49

+++ basename /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher

++ exit_1_banner 'Error on or near line 49 :: bootstrap_launcher '

+++ basename /opt/git/SmalltalkAustralia/GsDevKit_home/alt_bin/bootstrap_launcher

++ printf '\033[91;1m%s :: bootstrap_launcher \033[0m\n' 'Error on or near line 49 :: bootstrap_launcher '

Error on or near line 49 :: bootstrap_launcher  :: bootstrap_launcher 

++ exit 1

…which is correct, my default install of OSX does not have ‘realpath’ on the command line.

What would you recommend here? I can install a version of realpath, but I’m assuming that you want something that runs out-of-the-box.

I've already got a cross linux/mac implementation of realpath in `${GS_HOME}/bin/private/shFunctions`, so adding ${GS_HOME}/bin/private/shFunctions to $GS_HOME/alt_bin/gsdevkit_launcher should address that problem ...

I have some time on the weekend to play more so I’ll get back to it then.

sounds great ... if you want to open a pull request against issue_260 with your changes (this weekend would be fine) we can get your fixes into issue_260 for any other contributors to take advantage of  ... I've added you to the issue_260 team.

Dale

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Dale,

I'm setting up a Centos 7 for issue_260.

Before we proceed with:
https://github.com/GsDevKit/GsDevKit_home/tree/issue_260/shared/repos/GsDevKit_launcher#gsdevkit_launcher

We should create a 3.5 stone like:
git clone https://github.com/GsDevKit/GsDevKit_home.git
cd GsDevKit_home
. bin/defHOME_PATH.env    # define GS_HOME env var and put $GS_HOME into
PATH
installServerClient
createStone devKit_35 3.5
createClient tode1

Is this necessary ? or it is all included in
`$GS_HOME/alt_bin/bootstrap_launcher` ?

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

On 11/1/19 9:37 AM, BrunoBB via Glass wrote: Do do issue_260 development in a fresh GsDevKit_home installation ...
this is required
> createStone devKit_35 3.5

$GS_HOME/alt_bin/bootstrap_launcher creates a stone that is suitable for
doing iss_260 development (installs all of the necessary prereqs and a
set of bash scripts[1] for building/rebuilding the stone

[1]
https://github.com/GsDevKit/GsDevKit_home/tree/issue_260/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/gsdevkit_home 


> createClient tode1
You do need to create a fresh tode client so this step is necessary

Dale

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Dale,

i got an error executing:
updateGsDevKit -gdtcs

=================
   GsDevKit script: create_gs_server_image -f -d
/home/gemstone/GsDevKit_home/shared/pharo gsDevKitCommandLine
              path:
/home/gemstone/GsDevKit_home/shared/bin/create_gs_server_image
=================
create gsDevKitCommandLine.image image using
/home/gemstone/GsDevKit_home/sys/default/pharo/gsDevKitCommandLineLoad.st
Could not open the pharo image file
`/home/gemstone/GsDevKit_home/shared/pharo/gsDevKitCommandLine.image'.

There are three ways to open a pharo image file.  You can:
  1. Put copies of the default image and changes files in this directory.
  2. Put the name of the image file on the command line when you
     run pharo (use the `-help' option for more information).
  3. Set the environment variable PHARO_IMAGE to the name of the image
     that you want to use by default.

For more information, type: `man pharo' (without the quote characters).
Error on or near line 137 :: create_gs_server_image -f -d
/home/gemstone/GsDevKit_home/shared/pharo gsDevKitCommandLine ::
create_gs_server_image -f -d /home/gemstone/GsDevKit_home/shared/pharo
gsDevKitCommandLine
Error on or near line 74 :: devKitCommandLine -F :: devKitCommandLine -F
Error on or near line 189 :: updateGsDevKit -gdtcs :: updateGsDevKit -gdtcs

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Dale,

The execution sequence was:

cd $GS_HOME
git fetch --all
git checkout master
git pull origin master
updateGsDevKit -gdtcs



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hi Bruno,

I got the same thing on the Mac but just selected the image $GS_HOME/shared/pharo/gsDevKitTmp.image

Since this is a one time thing, and the goal is to remove the Pharo command line, you may be able to do the same thing. When Pharo attempts to launch to build the commandLineImage does it give you an option to select an image?

Cheers,

J

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Bruno,

The error is occuring because the file
`/home/gemstone/GsDevKit_home/shared/pharo/gsDevKitCommandLine.image'
does not exist and this guy is the devKitCommandLine image ...

So I assume that you are running into this problem, because you are
running in a fresh GsDevKit_home installation ... the
gsDevKitCommandLine.image is lazily created...

In your particular case, you can skip `updateGsDevKit -gdtcs`
altogether, because you have a fresh checkout of GsDevKit_home and the
`updateGsDevKit` step isonly necessary if you are using an existing
GsDevKit_home installation for issue_260 development ...

Dale

On 11/1/19 2:02 PM, BrunoBB via Glass wrote: _______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Jupiter,

I just fixed my problem with:
export PATH=$GS_HOME/alt_bin:$PATH
updateGsDevKit -gdtcs

From documentation:
The gsdevkit_launcher shell interpreter is in $GS_HOME/alt_bin, so
$GS_HOME/alt_bin needs to be located in your path.

When it failed $GS_HOME/alt_bin was not in PATH.

regards,
bruno




--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Dale,

After executing:
$GS_HOME/alt_bin/bootstrap_launcher

i got the following:

...finished :: createStone -g gsdevkit_launcher_350 3.5.0
+ /home/gemstone/GsDevKit_home/alt_bin/install_launcher.st --clone
--populate=gsdevkit_launcher_350
/home/gemstone/GsDevKit_home/alt_bin/gsdevkit_launcher: line 36: realpath:
command not found
UserDefinedError: File read failed:
+ pushd /home/gemstone/GsDevKit_home/server/stones/gsdevkit_launcher_350
~/GsDevKit_home/server/stones/gsdevkit_launcher_350
~/GsDevKit_home/shared/gemstone ~/GsDevKit_home
+ ./newBuild_SystemUser_gsdevkit_launcher_tode
/home/gemstone/GsDevKit_home/alt_bin/bootstrap_launcher: line 49:
./newBuild_SystemUser_gsdevkit_launcher_tode: No such file or directory
++ error 49
++ local lineno=49
+++ basename /home/gemstone/GsDevKit_home/alt_bin/bootstrap_launcher
++ exit_1_banner 'Error on or near line 49 :: bootstrap_launcher '
+++ basename /home/gemstone/GsDevKit_home/alt_bin/bootstrap_launcher
++ printf '\033[91;1m%s :: bootstrap_launcher \033[0m\n' 'Error on or near
line 49 :: bootstrap_launcher '
Error on or near line 49 :: bootstrap_launcher  :: bootstrap_launcher
++ exit 1


GS 3.5 is running !!!

gemstone@ubuntu:~/GsDevKit_home$ stones

Installed Stones:
        3.5.0   gsdevkit_launcher_350
Running Stones:
        Status       Version    Owner    Pid   Port   Started     Type      
Name
        -------     --------- --------- ----- ----- ------------ ------    
----
        exists       3.5.0     gemstone     22634 48219 Nov 01 14:25 Stone      
gsdevkit_launcher_350
Running Netldis:
        Status       Version    Owner    Pid   Port   Started     Type      
Name
        -------     --------- --------- ----- ----- ------------ ------    
----
        exists       3.5.0     gemstone     22706 53325 Nov 01 14:25 Netldi    
gsdevkit_launcher_350_ldi


Not sure the meaning of the errors:
/home/gemstone/GsDevKit_home/alt_bin/gsdevkit_launcher: line 36: realpath:
command not found
UserDefinedError: File read failed:

/home/gemstone/GsDevKit_home/alt_bin/bootstrap_launcher: line 49:
./newBuild_SystemUser_gsdevkit_launcher_tode: No such file or directory
++ error 49

++ printf '\033[91;1m%s :: bootstrap_launcher \033[0m\n' 'Error on or near
line 49 :: bootstrap_launcher '
Error on or near line 49 :: bootstrap_launcher  :: bootstrap_launcher






--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hi Bruno,
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Dale,

Tracking the errors (at least in my installation) and it seems that
$ROWAN_PROJECTS_HOME is not defined.

Because i change that variable in some scripts with hardcoded path and i was
able to go further but eventually failed at:
/home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/bin/bootstrap_install_tode.tpz

Because /usr/local/bin/smalltalk/gemstone/topaz does not exist, the actual
error:

/home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/gsdevkit_home/newBuild_SystemUser_gsdevkit_launcher_tode:
/home/gemstone/GsDevKit_home/shared/repos/GsDevKit_launcher/bootstrapping/gemstone/bin/bootstrap_install_tode.tpz:
/usr/local/bin/smalltalk/gemstone/topaz: bad interpreter: No such file or
directory

Maybe i'm doing something wrong i will check again later ...

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hi,

Now i'm in the same page as Jupiter.

There were some errors with variables but it was because i defined variables
with export command rather than in .profile file (in Ubuntu) and it seems
scripts has no knowledge of shell variables.

No i get "realpath: command not found".

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

On 11/1/19 3:50 PM, BrunoBB via Glass wrote:
> Dale,
>
> Tracking the errors (at least in my installation) and it seems that
> $ROWAN_PROJECTS_HOME is not defined.

ROWAN_PROJECTS_HOME is supposed to be added to the custom_stone.env file
in the install_launcher.st script[1], called on this line[2] in the
bootstrap_launcher script -- there is stop/start netldi following that
to ensure that ROWAN_PROJECTS_HOME gets set for all topaz sessions
launched against that stone ...

Could you have somehow bypassed that step?

I think that if you want to install in a freshly cloned GsDevKit_home
instance, you should just skip the initial `updateGsDevKit -gdtcs` and
then you'd be fine after that ...

I ran my tests in a separate GsDevKit_home instance (not freshly cloned,
so the devKitCommandLine image had already been defined ... just
invoking `devKitCommandLine` in a fresh clone, should build the
devKitCommandLine image) and every time I ran into an error I would
checkout the master version delete the shared/gemstone directory, fix my
scripts (in another close) push to issue_260 and then do a fresh
checkout and pull and then run the scripts from the beginning ...

You should not have to edit scripts and hardcode paths...

[1]
https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/shared/repos/GsDevKit_launcher/rowan/tonel/gsdevkit_launcher-Scripts/GdkL_Install_Launcher.class.st#L128-L152
[2]
https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/alt_bin/bootstrap_launcher#L47
This error is also a result of not running the install_launcher.st
script[1] ... you are missing symbolic links that are created here[3].

Perhaps you should try to install in a fresh clone and skip the
`updateGsDevKit -gdtcs` step?

Dale

[3]https://github.com/GsDevKit/GsDevKit_home/blob/issue_260/shared/repos/GsDevKit_launcher/rowan/tonel/gsdevkit_launcher-Scripts/GdkL_Install_Launcher.class.st#L156-L169
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Jupiter,

I take it that you have been able to get gsdevkit_launcher installed? Have you run the example scripts successfully?

# test out the example scripts
hello.st
error.st
error.st -D --

Dale

Hi Bruno,

I got the same thing on the Mac but just selected the image $GS_HOME/shared/pharo/gsDevKitTmp.image

Since this is a one time thing, and the goal is to remove the Pharo command line, you may be able to do the same thing. When Pharo attempts to launch to build the commandLineImage does it give you an option to select an image?

Cheers,

J

On 2 Nov 2019, at 8:02 am, BrunoBB via Glass [hidden email] wrote:

Dale,

i got an error executing:
updateGsDevKit -gdtcs

=================
  GsDevKit script: create_gs_server_image -f -d
/home/gemstone/GsDevKit_home/shared/pharo gsDevKitCommandLine
             path:
/home/gemstone/GsDevKit_home/shared/bin/create_gs_server_image
=================
create gsDevKitCommandLine.image image using
/home/gemstone/GsDevKit_home/sys/default/pharo/gsDevKitCommandLineLoad.st
Could not open the pharo image file
`/home/gemstone/GsDevKit_home/shared/pharo/gsDevKitCommandLine.image'.

There are three ways to open a pharo image file.  You can:
 1. Put copies of the default image and changes files in this directory.
 2. Put the name of the image file on the command line when you
    run pharo (use the `-help' option for more information).
 3. Set the environment variable PHARO_IMAGE to the name of the image
    that you want to use by default.

For more information, type: `man pharo' (without the quote characters).
Error on or near line 137 :: create_gs_server_image -f -d
/home/gemstone/GsDevKit_home/shared/pharo gsDevKitCommandLine ::
create_gs_server_image -f -d /home/gemstone/GsDevKit_home/shared/pharo
gsDevKitCommandLine
Error on or near line 74 :: devKitCommandLine -F :: devKitCommandLine -F
Error on or near line 189 :: updateGsDevKit -gdtcs :: updateGsDevKit -gdtcs

regards,
bruno



--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

Hi,

Now i'm in the same page as Jupiter.

There were some errors with variables but it was because i defined variables
with export command rather than in .profile file (in Ubuntu) and it seems
scripts has no knowledge of shell variables.

So you had to hand edit things? The script should have defined all of the needed env vars in custom_stone.env and other than $GS_HOME you shouldn't have to mess with .profile files ... which env vars did you define in .profile files?

No i get "realpath: command not found".

... and this is the edit that I (thought) I had asked Jupiter to make ...

I was busy with family (my birthday:) over the weekend, so I apologize for not getting involved earlier ....  I appreciate the fact that you and Jupiter took the time to figure things out ....

I'm kinda concerned that without making changes to the README and scripts, the next person to try will also fail, so any of the manual steps that both you and Jupiter took need to be addressed ...

AFAICT, there are two errors

1. realpath on Mac --- are you running on a Mac or a LInux box or ???
2.  the unconditional `updateGsDevKit -gdtcs` ... which is only needed if you are going to do development in an existing GsDevKit_home installation ...
   

I'm developing on Linux, so realpath was not a problem (Jupiter do you have a fix, or are you waiting for me to patch the problem) ... and I skipped the `updateGsDevKit -gdtcs` step when I was doing my testing (without trying the full process on a virgin clone) and things ran smoothly for me ...

Sooo if there are other problems I guess I need to be able to reproduce them in my environment so that I can figure out what needs to be fixed ...

Also we should probably take this discussion over to the issue_260 discussion list[1]

Dale

[1] https://github.com/orgs/GsDevKit/teams/issue_260

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

I've opened an issue_260 team discusstion[1] for further discussion on this topic.

Dale

[1] https://github.com/orgs/GsDevKit/teams/issue_260/discussions/1

On 11/4/19 9:52 AM, BrunoBB via Glass wrote:

Hi,

Now i'm in the same page as Jupiter.

There were some errors with variables but it was because i defined variables
with export command rather than in .profile file (in Ubuntu) and it seems
scripts has no knowledge of shell variables.

So you had to hand edit things? The script should have defined all of the needed env vars in custom_stone.env and other than $GS_HOME you shouldn't have to mess with .profile files ... which env vars did you define in .profile files?

No i get "realpath: command not found".

... and this is the edit that I (thought) I had asked Jupiter to make ...

I was busy with family (my birthday:) over the weekend, so I apologize for not getting involved earlier ....  I appreciate the fact that you and Jupiter took the time to figure things out ....

I'm kinda concerned that without making changes to the README and scripts, the next person to try will also fail, so any of the manual steps that both you and Jupiter took need to be addressed ...

AFAICT, there are two errors

1. realpath on Mac --- are you running on a Mac or a LInux box or ???
2.  the unconditional `updateGsDevKit -gdtcs` ... which is only needed if you are going to do development in an existing GsDevKit_home installation ...
   

I'm developing on Linux, so realpath was not a problem (Jupiter do you have a fix, or are you waiting for me to patch the problem) ... and I skipped the `updateGsDevKit -gdtcs` step when I was doing my testing (without trying the full process on a virgin clone) and things ran smoothly for me ...

Sooo if there are other problems I guess I need to be able to reproduce them in my environment so that I can figure out what needs to be fixed ...

Also we should probably take this discussion over to the issue_260 discussion list[1]

Dale

[1] https://github.com/orgs/GsDevKit/teams/issue_260

_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass