<br><br><div class="gmail_quote">On Thu, Mar 14, 2013 at 3:00 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@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 class="im">On 13 March 2013 22:41, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
><br>
> On Tue, Mar 12, 2013 at 2:13 PM, Nicolas Cellier<br>
> <<a href="mailto:nicolas.cellier.aka.nice@gmail.com">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br>
>><br>
>> It seems that this one would pass after a Compiler recompileAll, maybe<br>
>> we should add some postInstall action somewhere after environments<br>
>> changes...<br>
><br>
><br>
> Yes, but a simple recompile will result in lots of unbound methods. We need<br>
> to do something more principled that I thought ReleaseBuilder did. Frank,<br>
> you were working on this right?<br>
<br>
</div>Yes, but this is _before_ the ReleaseBuilderFor4dot5 kicks in. The<br>
tests are failing in the SqueakTrunk job, and it's only<br>
ReleaseSqueakTrunk that does all this (specifically, `Compile<br>
recompileAll`). And of course it's a one-way trip;<br>
ReleaseSqueakTrunk's artifact isn't fed back into SqueakTrunk. (And it<br>
shouldn't, because ReleaseSqueakTrunk is supposed to take an<br>
ever-shrinking trunk core and add expected goodies to produce a<br>
standard image.)<br>
<br>
Er, unless I miss the point: are you asking if we do any better than<br>
`Compiler recompileAll`?<br></blockquote><div><br></div><div>No. I'm saying that if an update causes the need for a recompilation then we need to do better than Compiler recompileAll because the naive Compiler recompileAll creates lots of unbound methods. We need to follow Compiler recompileAll with the relevant release magic to restart processes holding onto now obsolete methods etc. So that release magic ought to be in the base image as a facility. e.g. Smalltalk recompileAll might be much smarter than Compiler recompileAll. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
>> <a href="http://build.squeak.org/job/SqueakTrunk/223/testReport/Tests.Compiler/MethodHighlightingTests/testMethodHighlighting/" target="_blank">http://build.squeak.org/job/SqueakTrunk/223/testReport/Tests.Compiler/MethodHighlightingTests/testMethodHighlighting/</a><br>
>><br>
>> Nicolas<br>
>><br>
><br>
><br>
><br>
> --<br>
> best,<br>
> Eliot<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>