<html><body bgcolor="#FFFFFF"><div><br><br><div><br></div></div><div><br>On 2009-09-07, at 4:47 PM, Andreas Raab <<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>> wrote:<br><br></div><div></div><br><blockquote type="cite"><div><span>The reason why there is currently no unique update number associated with the trunk is only because nobody thus far has made a proposal as to how it should be defined. If anyone has a proposal for what to use, please make suggestions.</span><span class="Apple-style-span" style="color: rgb(148, 0, 14);"><br></span></div></blockquote><br><div>Well, the obvious way would be to create a Squeak package with no code, but with dependencies on all the packages in the trunk. Then you save a new verison of Squeak at each "stable" point in the evolution of the underlying packages. Voilà, a unique number that represents the state of all the code in the trunk. <span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); ">Not sure if there would be scaling issue with that many dependencies, but it's worth a try.</span></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.285156); -webkit-composition-fill-color: rgba(175, 192, 227, 0.21875); -webkit-composition-frame-color: rgba(77, 128, 180, 0.21875);"><br></span></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); ">Colin </span></div></body></html>