About MC for managing the image

[Daniel Vainsencher]

Yes, small relevant detail. The way we did it is
| vm names |
names _ 'EToys-dvf.1.mcz
Kernel-dvf.35.mcz
Network-dvf.16.mcz
Tools-dvf.28.mcz
MorphicExtras-dvf.1.mcz
Movies-dvf.2.mcz
FlexibleVocabularies-dvf.1.mcz
MorphicTests-dvf.4.mcz
BalloonMMFlash-dvf.1.mcz
Nebraska-dvf.3.mcz
ST80-dvf.17.mcz
StarSqueak-dvf.3.mcz
Graphics-dvf.13.mcz
Files-dvf.8.mcz
Speech-dvf.4.mcz
System-dvf.41.mcz
Balloon-dvf.5.mcz
Multilingual-dvf.6.mcz
Sound-dvf.2.mcz
SMBase-dvf.69.mcz
Compiler-dvf.12.mcz
Protocols-dvf.4.mcz
Collections-dvf.29.mcz
Morphic-dvf.45.mcz' findTokens: ' ', String cr.

vm _ MCVersionMerger new.
names do: [:fn | vm addVersion: (self loadVersionFromFileNamed: fn)].
vm merge

Where the dvf versions are the post morphic-split versions. The snippet 
above uses the same simultaneous merging that merging Squeak with lots 
of dependencies should use. That's pretty much what's going to be in the 
modified configs, except now its time for me to go catch a bus.

Daniel

stéphane ducasse wrote:
> This is an excellent news!
> 
> 
> On 19 sept. 05, at 12:40, Daniel Vainsencher wrote:
> 
>> Ok, so we've done this exercise with simul-merge, also encountered  
>> the same kinds of problems. Now it looks like its working - we got  an 
>> image with the MorphSplit work merged in.
>>
>> You can try it out with MC version 274 from squeaksource. at this  
>> point use merge not load, because merge is what we looked at.
>>
>> Avi and Daniel
>>
>> stéphane ducasse wrote:
>>
>>> Hi guys
>>> as a case study do the following:
>>> take the latest image we put on the ftp then
>>>     - create squeak package and add all the packages as required
>>>     - save squeak.1 package
>>>     - take the cs from http://webs.sinectis.com.ar/jmvuletich/  
>>> MorphicSplitters01.st
>>>     - load it add the new package to squeak
>>>     - save squeak.2 package
>>>     - quit
>>>     - take a fresh image and try to load.
>>>     with me it failed.
>>>     May be I should remove the dependencies between the package  
>>> that  the morphic splitters defined.
>>>     I will redo the experience to check.
>>> Now I tried to find a load order for the packages and I failed too.
>>> So now I'm stuck and I guess that for now. I consider   
>>> MorphicSplitters not usable
>>> Read more: Re: [ANN] [RFC] MorphicSplitters phase 1 completed
>>> Stef
>>
>>
> 
>