INI file in 2.0 one-click and Win-Executable

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

INI file in 2.0 one-click and Win-Executable

Torsten Bergmann
The new one-click on the CI server contains
an *.ini file.

But it is named CogVM.ini and since the VM
is called NBCog.exe it's useless.


Maybe this is already taken care of since
I've seen a thread about the naming of the VM.

IMHO we should have:
  - Pharo.exe
  - Pharo.ini

and a resource section within the executable that
contains the details about the VM type (Cog, NB, ...), the distributor
and (file) version.

We already discussed this in 2011 (!) here:

http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/49287

and it is a shame that we made no progress for such
simple enhancements.

Thanks
Torsten


Reply | Threaded
Open this post in threaded view
|

Re: INI file in 2.0 one-click and Win-Executable

EstebanLM
Hi,

we already have that!
problem is that build is broken since one month now and we still didn't find the time for fixing it (also there were a jenkins slave causing us problems).
but it will be ready for 2.0 release

Esteban

On Feb 10, 2013, at 8:00 PM, "Torsten Bergmann" <[hidden email]> wrote:

> The new one-click on the CI server contains
> an *.ini file.
>
> But it is named CogVM.ini and since the VM
> is called NBCog.exe it's useless.
>
>
> Maybe this is already taken care of since
> I've seen a thread about the naming of the VM.
>
> IMHO we should have:
>  - Pharo.exe
>  - Pharo.ini
>
> and a resource section within the executable that
> contains the details about the VM type (Cog, NB, ...), the distributor
> and (file) version.
>
> We already discussed this in 2011 (!) here:
>
> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/49287
>
> and it is a shame that we made no progress for such
> simple enhancements.
>
> Thanks
> Torsten
>
>


Reply | Threaded
Open this post in threaded view
|

Re: INI file in 2.0 one-click and Win-Executable

Marcus Denker-4
In reply to this post by Torsten Bergmann

On Feb 10, 2013, at 8:00 PM, Torsten Bergmann <[hidden email]> wrote:

> The new one-click on the CI server contains
> an *.ini file.
>
> But it is named CogVM.ini and since the VM
> is called NBCog.exe it's useless.
>
>
> Maybe this is already taken care of since
> I've seen a thread about the naming of the VM.
>
> IMHO we should have:
>  - Pharo.exe
>  - Pharo.ini
>
> and a resource section within the executable that
> contains the details about the VM type (Cog, NB, ...), the distributor
> and (file) version.
>
> We already discussed this in 2011 (!) here:
>
> http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/49287
>
> and it is a shame that we made no progress for such
> simple enhancements.
>

Yes, we made the one click work the last working build of the VMs we
could find, which was NBCog.

We need to get the build working and get the VM from there. This will be
Pharo.exe

And for 3.0 we should have

        -> real installers for every platform
        -> They come with a read-only image as part of the install that
            is started when you start the VM form e.g. the start menu
        -> Save then saves the VM like a document to the users dir
        -> klicking on such an image starts it
        ->This image is one file, simplifying everything.

        Marcus