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.

On Aug 28, 2006, at 5:17 AM, Colin Putney wrote:

>
> On Aug 28, 2006, at 4:42 AM, goran at krampe.se wrote:
>
>> Mmmm. So if we skip the idea of turning this into a cs - then I  
>> think it
>> is as simple as a cs with a preamble (or postscript) that does:
>>
>> 	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? This  
> has been a real pain, as I don't use 3.9 for production work.
>
> Colin
>