<br><br><div class="gmail_quote">On Mon, May 10, 2010 at 9:53 PM, laurent laffont <span dir="ltr">&lt;<a href="mailto:laurent.laffont@gmail.com" target="_blank">laurent.laffont@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

 <br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
VMMaker class&gt;&gt;updateFromServer should now load FT2Plugin from the new<br>
FreetypePlugin repository. A similar update will be needed for<br>
ConfigurationOfVMMaker for Pharo.<br></blockquote><div><br></div><div>Done  (version 1.4). All Pharo-1.0 tests green with last squeakvm revision.</div><div class="gmail_quote"><br></div></div></blockquote><div><br>Hi Laurent. Thank you very much for tacking care. Now I was thinking: the ONLY way to correclty be able to reproduce a VM version we need not only the VMMaker side but also SVN. If 6 months from today, I try to load version 1.4 with trunk, it won&#39;t work. I need to downloa an spceific SVN revision, as you write it in the commit comment. However, I was thinking that it would be great to put such information in the description: of Metacello. Not even the version (as the repo can change) but also the whole command. Not necesary while a verison is in #development but yes when it is realed. So, suppose I release 1.4 I can write:<br>

<br>version14: spec <br>    &lt;version: &#39;1.4&#39; imports: #(&#39;1.4-baseline&#39;) &gt;<br>    <br>    spec for: #common do: [<br>        spec blessing: #development.<br>        spec description: &#39;- Changed repository of TrueType<br>
                               - etc.....<br>                                Works with svn co <a href="http://squeakvm.org/svn/squeak/trunk/platforms/">http://squeakvm.org/svn/squeak/trunk/platforms/</a> -r 2203&#39;.<br>
        spec <br>            package: &#39;FFI-Pools&#39; with: &#39;FFI-Pools-ar.1&#39;;<br>            package: &#39;SharedPool-Speech&#39; with: &#39;SharedPool-Speech-dtl.2&#39;;<br>            package: &#39;VMMaker&#39; with: &#39;VMMaker-dtl.170&#39;;<br>
            package: &#39;MemoryAccess&#39; with: &#39;MemoryAccess-dtl.3&#39;;<br>            package: &#39;SlangBrowser&#39; with: &#39;SlangBrowser-dtl.3&#39;;<br>            package: &#39;VMConstruction-Plugins-OSProcessPlugin&#39; with: &#39;VMConstruction-Plugins-OSProcessPlugin-mtf.21&#39;;<br>
            package: &#39;VMConstruction-Plugins-AioPlugin&#39; with: &#39;VMConstruction-Plugins-AioPlugin-dtl.9&#39;;<br>            package: &#39;VMConstruction-Plugins-XDisplayControlPlugin&#39; with: &#39;VMConstruction-Plugins-XDisplayControlPlugin-dtl.7&#39;;<br>
            package: &#39;Balloon3D-Constants&#39; with: &#39;Balloon3D-Constants-ar.5&#39;;            <br>            package: &#39;Balloon3D-Plugins&#39; with: &#39;Balloon3D-Plugins-bf.5&#39;;                                 <br>
            package: &#39;Freetype-Plugin&#39; with: &#39;Freetype-Plugin-dtl.56&#39;;<br>            package: &#39;FreeType&#39; with: &#39;FreeType-tween.435&#39;.<br>    ].<br><br>    spec for: #pharo do: [<br>        spec blessing: #development.<br>
        spec <br>            package: &#39;Alien-VMMaker-Support&#39; with: &#39;Alien-VMMaker-Support-John M McIntosh.8&#39;;<br>            package: &#39;Alien-VMMaker-Plugins&#39; with: &#39;Alien-VMMaker-Plugins-John M McIntosh.8&#39;;<br>
            package: &#39;Sound&#39; with: &#39;Sound-StephaneDucasse.47&#39;.<br>    ]            <br><br><br><br>Of course, this is just an example...<br><br>what do you think ? I hope this will increase traceability between Smalltalk code and svn. <br>
<br>Cheers<br><br>Mariano<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div class="gmail_quote"></div>
Laurent Laffont<br>
<br><a href="http://pharocasts.blogspot.com/" target="_blank">http://pharocasts.blogspot.com/</a><br>

<a href="http://magaloma.blogspot.com/" target="_blank">http://magaloma.blogspot.com/</a><br><div><br></div></div>
<br></blockquote></div><br>