<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On Jan 28, 2015, at 11:21 AM, Chris Cunningham <<a href="mailto:cunningham.cb@gmail.com">cunningham.cb@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">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.<div>Yes, it does require loading them in a specific order.</div><div>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.</div></div></div></blockquote><div><br></div><div><br></div>Right. And the way to manage that order dependency is with a configuration. You commit the version of pkg2 with the class moved into it from pkg1. You create and commit a configuration for that state (new pkg2, old pkg1). Then you commit the new pkg2 with the class missing.<div><br></div><div>The configuration ensures that the new pkg2 is loaded b4 the new pkg1, and hence that the class is not lost.</div><div><br></div><div>Search the list for info in Monticello configs. There's a menu pick to open the MCConfigurationBrowser which will help.</div><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>-cbc</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 28, 2015 at 11:12 AM, Michal <span dir="ltr"><<a href="mailto:michal-list@auf.net" target="_blank">michal-list@auf.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
hi Marcel -<br>
<br>
Thanks for your answer, and yes, I should have been clearer:<br>
<span class=""><br>
> What exactly did you do? :)<br>
<br>
</span>A version of this:<br>
<span class=""><br>
> Having a system with old Pkg1 to update with new version, C will be removed.<br>
<br>
</span>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).<br>
<br>
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:<br>
<br>
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?<br>
<br>
<br>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span></span><br></div></blockquote></div></body></html>