Sounds like a lot of fun to learn, but it also sounds like you need a lot more expert knowledge than I have!
Take care, Rob On Mon, Mar 9, 2009 at 4:14 PM, Stéphane Ducasse <stephane.duca...@inria.fr>wrote: > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
