VMs version name

> Smalltalk vm version
>
> will give you a full response :)
>
>
> On 2013-02-01, at 23:05, Francois Stephany <[hidden email]> wrote:
>
>> Is there a way to identify a VM with a version number like an image? When I download the latest 'Pharo.app' it says "Pharo VM 6.0-pre". It's the same name that the VM I downloaded one month ago.
>>
>> Is there something like the image name (e.g, "2.0-497") I can use to tell someone to use a given VM version?
>>
>>
>> Cheers,
>> Fa
>>
>
>

>> Smalltalk vm version
>> 'NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
>> NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
>> https://git.gitorious.org/cogvm/blessed.git Commit: 40ac7e7bdec6fef0e934d2c019b86db996053912 Date: 2012-11-19 18:54:49 +0100 By: Mariano Martinez Peck <[hidden email]> Jenkins build #146
>> '
>
>
> Indeed :p
>
> There's nothing shorter? Can't we use a shortified git commit id (http://git-scm.com/book/ch6-1.html) to identify a given VM? Or we have a mix of git versioning and Monticello versioning?

>
> On 2013-02-01, at 23:22, Francois Stephany <[hidden email]> wrote:
>
>>> Smalltalk vm version
>>> 'NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
>>> NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
>>> https://git.gitorious.org/cogvm/blessed.git Commit: 40ac7e7bdec6fef0e934d2c019b86db996053912 Date: 2012-11-19 18:54:49 +0100 By: Mariano Martinez Peck <[hidden email]> Jenkins build #146
>>> '
>>
>>
>> Indeed :p
>>
>> There's nothing shorter? Can't we use a shortified git commit id (http://git-scm.com/book/ch6-1.html) to identify a given VM? Or we have a mix of git versioning and Monticello versioning?
>
> currently there are 2 sources for the VM:
> - git sources from https://gitorious.org/cogvm/blessed/
> - VMMaker & Co from monticello
>
> to be precise we need both right now to properly identfy the VM.
> Future plans are to merge the sources and put VMMaker into the git repository as well.
>
> For now you could simply rely on the commit SHA since most often changes happen on
> both sides (and our builds were only triggered by changes in the git repos I think)...
>

>
> On 2013-02-01, at 23:22, Francois Stephany <[hidden email]> wrote:
>
> >> Smalltalk vm version
> >> 'NBCoInterpreter NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
> >> NBCogit NativeBoost-CogPlugin-IgorStasenko.15 uuid: 44b6b681-38f1-4a9e-b6ee-8769b499576a Nov 27 2012
> >> https://git.gitorious.org/cogvm/blessed.git Commit: 40ac7e7bdec6fef0e934d2c019b86db996053912 Date: 2012-11-19 18:54:49 +0100 By: Mariano Martinez Peck <[hidden email]> Jenkins build #146
> >> '
> >
> >
> > Indeed :p
> >
> > There's nothing shorter? Can't we use a shortified git commit id (http://git-scm.com/book/ch6-1.html) to identify a given VM? Or we have a mix of git versioning and Monticello versioning?
>
> currently there are 2 sources for the VM:
> - git sources from https://gitorious.org/cogvm/blessed/
> - VMMaker & Co from monticello
>
> to be precise we need both right now to properly identfy the VM.
> Future plans are to merge the sources and put VMMaker into the git repository as well.
>
> For now you could simply rely on the commit SHA since most often changes happen on
> both sides (and our builds were only triggered by changes in the git repos I think)...