Indeed. It was just I was in the middle of something.
Le 25/03/2017 à 19:10, Stephane Ducasse a écrit :
> you should think to move to Pharo 50. We closed around 1500 issues between
> pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.
> Pharo 50 is really stable and working
Hilaire
you should think to move to Pharo 50. We closed around 1500 issues between
pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.
Pharo 50 is really stable and working well
Stef
On Sat, Mar 25, 2017 at 8:58 AM, Hilaire wrote:
> Hi Sabine,
>
> Thanks to share your expe
Hi Sabine,
Thanks to share your experience.
My process is in 3 folds:
1. I build from bash and smalltalk scripts an application archive for
deployment, as I do for Dr.Geo (with configured image, VM, bootstart
data and bash scripts)
2. On the target host, the archive is deployed (unarchived), th
Hi Hilaire,
I also use a command line handler for start in a new image with voyage . I
start it like this on windows:
.\...\Pharo5.0.image --no-default-preferences eval --save "
MCRepositoryGroup default addRepository: (MCHttpRepository location: '
http://smalltalkhub.com/mc/Sabine/RKA24/main' u
If I open manualy this image execute the configureMyImage.st code from a
playground, then save the image, I don't have a Voyage time error at
start up.
Are there non friendly interaction between voyage/socket and st command
handler?
Hilaire
Le 22/03/2017 à 20:35, Hilaire a écrit :
> Hi,
>
> Whe
Hi,
When I configure a production image with command st handler as following:
pharo myImage st --save --quit configureMyImage.st
I notice at image start up, a Socket timeout error.
In the configureMyImage.st script, among other things, I open a
singleton Voyage repository. I added a 5s delay at
