Hi!

Todd Blanchard <tblanchard at mac.com> wrote:
> This is definitely a pain - when working in older images, SqueakMap  
> insists on updating - but the update fails because it expects apis  
> that are not in that image.
> 
> It needs to be smarter about matching SM client version to Squeak  
> image version - maybe I don't want to update.

It is not that simple. The server maintains the domain model - an
instance of SMSqueakMap. When you use the web UI to add packages, edit
releases etc - the server regularly makes an ImageSegment snapshot of
that SMSqueakMap instance.

The "client" images then have the exact same code - downloads the
ImageSegment and installs it into the image.

Net result: The client images need to have the same classes as the
server has. As it works *today* that is. I am not saying it couldn't
work differently.

Further:

> On Aug 28, 2006, at 5:17 AM, Colin Putney wrote:
> >> 	SMSqueakMap bootStrap
> >>
> >> ...that would upgrade it to the *current* SM - whatever that is at  
> >> the
> >> time of applying the update. But frankly, as SM works today there  
> >> is no
> >> other version you can use in order to communicate with the server.
> >
> > If I wanted to use SM in 3.8 and earlier in the meantime, could I  
> > execute this in a workspace to fix my local SM installation?

I am not sure I grok the above sentence. The oneliner upgrades the code
in the image to be the current version of SM that is on SM itself. This
is typically the remedy for the "SMMaintainableObject blabla error" (old
SM code in an old image trying to install a new ImageSegment). Since all
images in a directory share the same "sm" dir - when one has been
upgraded the other images will not detect this and needs the above
oneliner.

> > This  
> > has been a real pain, as I don't use 3.9 for production work.

Not sure what 3.9 has to do with it.

regards, Göran

PS. Unfortunately the upgrade of SM into 3.8 had an unfortunate side
effect causing SM to not work in 3.7 and older (IIRC). This has to do
with multi byte strings etc. And yes, SM needs a rewrite/overhaul but I
am swamped right now with other things. :)