Hi Dave,<div><br></div><div> thanks, but...<br><br><div class="gmail_quote">On Sat, Mar 9, 2013 at 7:06 AM, <span dir="ltr"><<a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Item was changed:<br>
----- Method: VMMaker class>>versionString (in category 'version testing') -----<br>
versionString<br>
<br>
"VMMaker versionString"<br>
<br>
+ ^'4.10.13'!<br>
- ^'4.10.12'!<br></blockquote><div><br></div><div>I *hate* the above. It is busy work (it must be done manually before each commit). It is really easy to forget to do. It is meaningless (because it is easy to forget it makes no guarantee that it identifies a unique version). It is not a good search key. Mapping the version number into the software configuration that produced the C code is hard (you have to trawl through Monticello packages searching for the version with the relevant version string; you can script this but fer christ's sake...).</div>
<div><br></div><div>Using the Monticello package name and version (with the dirty marker) on the other hand is automatic, is a really good key, and is meaningful. So please can we discard VMMaker versionString and move to using the Monticello package? Please? Please.</div>
</div>-- <br>best,<div>Eliot</div>
</div>