lukas
>>>
>> I can load the code.
>>
>> However there is no way around loading around 30 change-sets in the
>> right order. Perform all kinds of manual actions, like restarting
>> the GUI process, saving the image and reopening it.
>>
>> After having loaded the change-sets dozens of packages are dirty,
>> from Compiler, Kernel, Collection, Morphic, ... I can publish these,
>> but you won't be able to load them. Compiler, Encoder,
>> CompiledMethod, MethodContext, BlockContext, Debugger, ... there are
>> many changes that can't just be loaded like that and that require
>> complicated object migration at the right points in time.
I was more thinking
� � � �- produce a stream of cs and put it into the update stream
� � � �- then produce the clean packages so that we are able to load
incrementally (after the cs stream is loaded).
� � � �the update streams. (but sometimes in the past we were not able to
produce pakcages that
� � � �could be loaded)
This is clear that we still have a living system.
Stef