Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

Eliot Miranda eliot.miranda at gmail.com
Thu Jun 16 20:07:23 UTC 2016

Hi All,

     so after fixing "git remote get-url origin" to fail over to "git
remote show origin | filter and munge" the culture shock of "git commit -a"
(git commit does nothing ?!?!?) I have a VM that outputs a reasonable
version info:

5.0 5.0.201606161953 Mac OS X built on Jun 16 2016 12:56:52 PDT Compiler:
4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57) [Production Spur VM]
CoInterpreter VMMaker.oscog-eem.1886 uuid:
d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016
StackToRegisterMappingCogit VMMaker.oscog-eem.1886 uuid:
d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016
VM: r201606161953 http://github.com/OpenSmalltalk/vm $ Date: Thu Jun 16
12:53:33 2016 -0700 $
Plugins: r201606161953 http://github.com/OpenSmalltalk/vm $

Which begs the question how do I differentiate this from something built
officially via Travis?  Arguably the URL is wrong, and should only say "
http://github.com/OpenSmalltalk/vm" for travis builds, and perhaps should
just include my local hostname and current directory when I make any kind
of local modification.  So the above would read

VM: r201606161953 McStalker:?users/eliot/oscogvm $ Date: Thu Jun 16
12:53:33 2016 -0700 $
Plugins: r201606161953 McStalker:?users/eliot/oscogvm $

Alternatively we could add another field, or modify one of the existing
fields to say "I'm official" however one would do that.  I don't know how,
I just know we need this.  I shouldn't be able to pollute the VM pool by
putting some VM on some site somewhere that i just happened to build after
several sherries and some cannabis brownies that looks to all intents and
purposes just like a VM built by our official Travis slaves.  Hic.  Chillin'

best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160616/01f1e9c4/attachment.htm

More information about the Vm-dev mailing list