On 8 January 2018 at 19:45, Eliot Miranda <[email protected]> wrote:
> Hi Ben,
>
>     I think that the hash is indeed that if a commit. And I thought someone
> had written a script to find the commit from the hash.  Alternatively you
> could look at the various system attributes the Squeak vm uses to identify
> itself.  I *think* the Pharo vm has the same info baked in.  In particular
> there should be the date of the commit.

E.g.:

$ pharo7 --version
5.0-201712221331  Tuesday 26 December  14:19:31 CET 2017 gcc 4.8.5
[Production Spur 64-bit VM]
CoInterpreter VMMaker.oscog-eem.2302 uuid:
55ec8f63-cdbe-4e79-8f22-48fdea585b88 Dec 26 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2302 uuid:
55ec8f63-cdbe-4e79-8f22-48fdea585b88 Dec 26 2017
VM: 201712221331
alistair@alistair-xps13:snap/pharo-snap/pharo-vm/opensmalltalk-vm $
Date: Fri Dec 22 14:31:01 2017 +0100 $
Plugins: 201712221331
alistair@alistair-xps13:snap/pharo-snap/pharo-vm/opensmalltalk-vm $
Linux cbc086ddd661 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4
15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
plugin path: /snap/pharo7/x1/usr/bin/pharo-vm/5.0-201712221331
[default: /snap/pharo7/x1/usr/bin/pharo-vm/5.0-201712221331/]


$ scripts/checkoutVMbyDate 'Fri Dec 22 14:31:01 2017 +0100'
Searching for date: (Fri Dec 22 14:31:01 2017 +0100)
Note: checking out 'ec439f18e994309de62f64c23b48e35920633f39'.
...


Cheers,
Alistair





> _,,,^..^,,,_ (phone)
>
> On Jan 8, 2018, at 6:36 AM, Ben Coman <[email protected]> wrote:
>
> This filename of the VM download url...
> http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201712211450-276a5ff.zip
>
> includes a hash "276a5ff" that I presumed identified the opensmalltalk-vm
> commit from which this VM was built. i.e. so I could check that out if I
> wanted to compile a debug version of that VM.
>
> However...
> $ git checkout 276a5ff
> says... error: pathspec '276a5ff' did not match any file(s) known to git.
>
> so what exactly is that hash 276a5ff in the filename?
>
> cheers -ben

Reply via email to