[Vm-dev] How to make a "point" release with opensmalltalk-vm?

Holger Freyther holger at freyther.de
Mon Mar 19 14:48:12 UTC 2018



> On 19. Mar 2018, at 14:39, Clément Bera <bera.clement at gmail.com> wrote:
> 


> Copying the appropriate text from the version info above:
> 
> $ Date: Fri Mar 16 11:38:09 2018 +0100 $
> 
> 
> $ git log | grep -B 3 "Fri Mar 16 11:38:09 2018 +0100"

This is one way but it can break once cherry-pick'ing is used (e.g. to maintain a branch). What was the reason not to use a commit number in the binary? This would uniquely identify it (as the sha1 depends on all parents).


> I'm not sure I understand the question.  But I think the answer you
> are looking for is that you need to load the matching version of
> VMMaker in to squeak.
> image/buildspurtrunkvmmakerimage.sh
> 
> Yes, the script image/buildspurtrunkvmmakerimage.sh gets you a working VM+image with VMMaker installed and then in Monticello you can load back 
> 
> CoInterpreter VMMaker.oscog-eem.2359 
> 
> which is the version you have a problem with. This is the easiest way.

Right. But then one has to do it for every plugin as well? In the case of pharo-vm the mc/ directory has 35 plugins in it. To me this doesn't sound like a very pleasant thing to do? What alternatives are there? Could the .mcz be copied somewhere (not necessarily to git)? Have links from UUID to URL of the package?


holger


More information about the Vm-dev mailing list