<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Bert,<br></div><div><br>On Jan 28, 2015, at 11:54 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">On 28.01.2015, at 20:47, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" class="">eliot.miranda@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">On Jan 28, 2015, at 11:21 AM, Chris Cunningham <<a href="mailto:cunningham.cb@gmail.com" class="">cunningham.cb@gmail.com</a>> wrote:</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">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 class="">Yes, it does require loading them in a specific order.</div><div class="">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 class=""><br class=""></div><div class=""><br class=""></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 class=""><br class=""></div><div class="">The configuration ensures that the new pkg2 is loaded b4 the new pkg1, and hence that the class is not lost.</div><div class=""><br class=""></div><div class="">Search the list for info in Monticello configs. There's a menu pick to open the MCConfigurationBrowser which will help.</div></div></div></blockquote></div><div class=""><br class=""></div><div class="">+1 on MCConfigs.</div><div class=""><br class=""></div><div class="">And didn’t we make them correctly handle moves between packages last year? I think you just need a single config with new versions of both Pkg1 and Pkg2.</div></div></blockquote><div><br></div><div><br></div>D'u remember how that works? I'm curious.<div><br><blockquote type="cite"><div><div apple-content-edited="true" class="">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; font-family: 'Lucida Grande'; font-size: 12px;"><div style="word-wrap: break-word;" class=""><div style="font-family: Helvetica;" class=""><span class="Apple-style-span" style="font-family: Helvetica;">- Bert -</span></div></div></span></div></div></blockquote></div><div><br style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Eliot (phone)</span></div></body></html>