Whoops, now copied to pharo-dev to continue discussion there. On Sun, Apr 16, 2017 at 9:13 PM, Ben Coman <btc@openinworld.com> wrote:
On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie <luke@snabb.co> wrote:
On 14 April 2017 at 22:20, Stephane Ducasse <stepharo.self@gmail.com> wrote:
This is what we always have when we release and we freeze it. The vm 60 will be compatible with latest pharo 60 image.
It is possible that I have misunderstood the whole situation and there is no problem at all. That would be awesome. Let's check :-) here is my understanding of the state of the world right now:
The latest stable image release is Pharo-50771.image. The latest stable VM source release is pharo-vm-2016.02.18. These two releases are not compatible: This interpreter (vers. 6505) cannot read image file (vers. 6521).
So the problem is that if a distribution packages the latest VM source release then the users won't be able to run the Pharo 5 VM that they download from pharo.org or via the pharo-launcher image.
Is that correct? If so that's fine and hopefully we can fix it for Pharo 6.0. But if I am misunderstanding and a fix is available today that would also be good to know.
I am looking for the "latest VM source release" in http://files.pharo.org/vm/src/vm-unix-sources/
and assuming that non-spur is the stable option for pre-6.0 images.
That is not correct. Pharo 5 used a Spur-VM since build 50496 circa 2015-12-14. * http://files.pharo.org/image/50-preSpur/ * http://files.pharo.org/image/50/
cheers -ben