marcel.taeumel wrote
> 
> marcel.taeumel wrote
>> Hey, there.
>> 
>> "update-mt.389.mcm" removes "311Deprecated".
>> "update-mt.390.mcm" removes "SmallLand".
>> 
>> This seems to work fine in a foreign, updated image. In the the that
>> created those update maps, however, those packages seem to return on
>> update. :-/ I suspect that there is some kind of bug when processing the
>> update maps...
>> 
>> Best,
>> Marcel
> Here is a thought:
> - The system seems to remember that the latest update config was
> "update-mt.387.mcm"
> - It starts processing "update-mt.388.mcm" (although I did create and
> upload it) loading "311Deprecated" and "SmallLand" again.
> - It starts processing "update-mt.389.mcm" (although I did create and
> upload it) not finding "311Deprecated" 
> there.
> - It starts processing "update-mt.390.mcm" (although I did create and
> upload it) not finding "SmallLand" there.
> 
> However, the #postLoad scripts in SqueakVersion where not executed again
> and hence I end up having "311Deprecated" and "SmallLand" in the image
> again. :-/
> 
> I see two ways to fix this:
> - If I create a new update config, remember that for the next update in
> the image.
> - Re-execute that post-load scripts again if possible
> 
> I prefer the first alternative.
> 
> Best,
> Marcel

Could this work:
http://forum.world.st/The-Inbox-MonticelloConfigurations-mt-146-mcz-tp4912486.html
?

Best,
Marcel



--
View this message in context: http://forum.world.st/Struggling-with-Update-Maps-tp4912474p4912487.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.