<div dir="ltr">Hi Yoshiki,<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 24, 2016 at 12:54 PM, Yoshiki Ohshima <span dir="ltr"><<a href="mailto:Yoshiki.Ohshima@acm.org" target="_blank">Yoshiki.Ohshima@acm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Jun 24, 2016 at 11:06 AM, tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br>
><br>
>> On 22-06-2016, at 7:40 PM, Yoshiki Ohshima <<a href="mailto:Yoshiki.Ohshima@acm.org">Yoshiki.Ohshima@acm.org</a>> wrote:<br>
>><br>
>> On Wed, Jun 22, 2016 at 7:27 PM, tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br>
>>>><br>
> {snip}<br>
>>><br>
>>> So far as I can see it can’t work because the ‘echo’ gives us a single line as an answer and my best guess (since man pages are so very carefully written to present a wall of text that makes no sense unless you already know the answer) is that the ‘sort’ expects some cr or nl in there. Thus we (probably) just get the one line and ‘head’ does nothing to help.<br>
>><br>
>> You're so right. It should be 'ls' instead of 'echo’.<br>
><br>
> Except that with the git based builds it looks like we are moving to a somewhat different numbering sequence and so comparing any possible old copies with new ones is going to become harder. For example, a freshly built Pi vm is tagged as 5.0-201606241150 (ie the date/time)<br>
<br>
</span>Oh... That is interesting. If the squeak VM package for the next<br>
release of Raspian follows this new scheme, is it true that we'd only<br>
have to support this format? Or people may install or keep older<br>
versions and we'd better support both?<br></blockquote><div><br></div><div>The VM is backward compatible (at least for Spur, which I think is the only format NuScratch has been released in) so there's no need to maintain older versions. A current VM should work. And with a little bit of trickery in the launch script one could have it update the VM at suitable times, for example when a serious VM bug is identified and fixed, or a significant performance increase has been achieved.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> I have no idea how we can solve that. Aside from the trivial solution of me including an explicit vm path in the Pi script, of course.<br>
<br>
</span>Ok.. Somebody should be able to write a few more shell commands to<br>
figure that out...<br><span class="HOEnZb"><font color="#888888"><br>
-- Yoshiki<br></font></span></blockquote></div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>