[Pharo-project] Monticello Version Info
dhenrich at vmware.com
Fri Mar 2 12:08:21 EST 2012
The last time I delved into the area there was one line of code in Monticello (I was looking at pharo) that compared the file UUID and it might have been involved in hashing. At one point the UUID calculation was broken in Pharo and noone noticed until they tried to load the package into GemStone (which is using an older version of Monitcello) and things went haywire:)
So yes the name is the primary lookup mechanism...
You might have gotten messed up by changing the name of the mcz file to NOT match the internal package name ... there are definitely expectations in the Monticello ecosystem that the package name and file name match at some level...
----- Original Message -----
| From: "Chris Cunningham" <cunningham.cb at gmail.com>
| To: Pharo-project at lists.gforge.inria.fr
| Sent: Friday, March 2, 2012 8:30:27 AM
| Subject: Re: [Pharo-project] Monticello Version Info
| On Fri, Mar 2, 2012 at 5:30 AM, Camillo Bruni
| <camillobruni at gmail.com> wrote:
| > But I am not completely sure how the internals work with MC, but
| > from my research
| > so far I am almost convinced that versions are found merely by
| > their name. Since
| > the VersionInfo does not track the repository it relates to.
| It does appear to find versions by name, but there is an internal id
| number that it uses to validate the file is the right one. I've been
| 'bitten' by this a few times - it is a really good idea to NOT rename
| MCZ files.
More information about the Pharo-dev