<div dir="ltr">Your patch should work either way. At the level where a repository retrieves Collections-ul.573 for you, it doesn't care whether its a .mcd or .mcz; the MCVersion object you get with its embedded Snapshot to patch, will have everything as if it were loaded from a mcz..</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 5:06 PM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div> I see through a web browser that <a href="http://source.squeak.org/trunk/Collections-ul.573.mcz" target="_blank">http://source.squeak.org/trunk/Collections-ul.573.mcz</a> exists but in an updated trunk image (Spur) with a repository browser on <a href="http://source.squeak.org/trunk" target="_blank">source.squeak.org/trunk</a> it shows me only that Collections-ul.573(nice.572).mcd exists. What gives?<br clear="all">
<div><br></div><div>For Spur I need to patch Collections-ul.573.mcz to Collections.spur-ul.573.mcz and the automated patch code assumes it can obtain the .mcz from trunk.<span class="HOEnZb"><font color="#888888"><br>-- </font></span></div>
<span class="HOEnZb"><font color="#888888">best,<div>Eliot</div>
</font></span></div></div>
<br><br>
<br></blockquote></div><br></div>