[Vm-dev] Need an Alien-Core-eem.102 update

[David T. Lewis]

Yes the Pharo tools caused the original issue, but here the only
problem is that Eliot did not remember to bump the version number up
to 102 when he fixed the problem. So the simple solution is to just
save it once more with 102 in the version name. I don't have write
access to that repo, so that's why I asked Eliot to do it.

Yes a .mcm would handle it also (but easier here to just save it
one more time). If you are interested in that approach, look at
update.oscog in the VMMaker repository. There are a few update
maps (totally unofficial and unsupported) that I have been saving
from time to time.

The 'update.oscog' maps correspond to oscog configurations, as
distinct from the 'update' .mcm maps that have been used for many
years as the update stream for the traditional interpreter VM.

Dave

On Wed, Jan 08, 2020 at 04:37:16PM +0100, Nicolas Cellier wrote:
>  
> Ah, I see, no timestamp thanks to Pharo tools...
> Maybe we could use a .mcm? or update Metacello ConfigurationOf(Old)Alien?
> 
> Le dim. 5 janv. 2020 ?? 01:10, David T. Lewis <lewis at mail.msen.com> a ??crit :
> 
> >
> > Hi Eliot,
> >
> > When you get a chance, can you please commit an update to
> > Alien-Core-eem.101
> > in http://www.squeaksource.com/Alien in order to make a Alien-Core-eem.102
> > version that will appear as the latest version for updates?
> >
> > This is needed because the image/BuildSqueakSpurTrunkVMMakerImage.st
> > is loading Alien-Core-TorstenBergmann.101 rather than the intended
> > Alien-Core-eem.101 as the latest Alien-Core version.
> >
> > Thanks,
> > Dave
> >
> >