On 3 November 2014 19:12, tim Rowledge tim@rowledge.org wrote:
On 03-11-2014, at 4:54 AM, Frank Shearar frank.shearar@gmail.com wrote:
Not only that, I don't think there's any way of saying "please update my Squeak image from 4.5-N to 4.5-M", so we can't recreate the starting conditions of a build.
Actually I think that we can do this. Take a look at UpdateStreamDownloader class>applyUpdatesFromDiskToUpdaeNumber:stopIfGap:
No, because decomposing a sum into its summands is not unambiguous. If you and I have two images, and your Network package is version 222 and Kernel package is 501, while my Network package is version 221 and Kernel is version 502, all other packages being the same, _our update numbers are identical_.
There are a few synchronisation points, in the form of MCMs, in the history of the update stream, but in between those, no, you have no way of knowing - from only the update number - what the versions of packages are that ought to make up that "version" of the image.
frank
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Klingon Code Warrior:- 9) "A TRUE Klingon warrior does not comment his code!"