On 2009-09-07, at 4:47 PM, Andreas Raab <andreas.raab at gmx.de> wrote:


> 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.

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. Not sure if there would be scaling  
issue with that many dependencies, but it's worth a try.

Colin 
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090907/e9ca3324/attachment.htm