If you load Pkg2 first, then the code will migrate over to that package
(making Pkg1 dirty).  Then loading Pkg1 would 'clean' it up.  doing this,
there should be no loss of the state during loading.
Yes, it does require loading them in a specific order.
And, yes, if you moved Class C from Pkg1 to Pkg2, and Class D from Pkg2 to
Pkg1 in the same commits, you need to figure out how to do simultaeous
loading.  Or, as I think is more common, don't do this all at once, but
rather do them as two steps with specif loading ordering.

-cbc

On Wed, Jan 28, 2015 at 11:12 AM, Michal <michal-list at auf.net> wrote:

>
> hi Marcel -
>
> Thanks for your answer, and yes, I should have been clearer:
>
> > What exactly did you do? :)
>
> A version of this:
>
> > Having a system with old Pkg1 to update with new version, C will be
> removed.
>
> That is: mv class C from Pkg1 to Pkg2 in a development image, load Pkg1
> and then Pkg2 in the server image (this is Seaside related).
>
> And yes, depending on the order of loading, C will come back, but it will
> have lost its state, if any, obviously. So the question stands, I think:
>
> What is the best way of moving a class from one mcz package to another,
> and then load those packages in a different image without ever getting C
> removed from the image?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20150128/45441c9c/attachment.htm