Yeah, if you could hold off on that change for a bit (this is for Pharo-2.0 right?)...I might have a different solution for Pharo-2.0...
----- Original Message -----
| From: "Stéphane Ducasse" <[hidden email]>
| To: [hidden email]
| Cc: [hidden email]
| Sent: Monday, July 23, 2012 1:41:58 AM
| Subject: Re: [Pharo-project] Change in MCCacheRepository that affects Metacello loading
| may be we should rollback this changes because it is not mandatory.
| On Jul 23, 2012, at 10:14 AM, Mariano Martinez Peck wrote:
| > Hi Dale. http://code.google.com/p/pharo/issues/detail?id=6405
| > renames MCCacheRepository #default to #uniqueInstance. Therefore,
| > to be able to bootstrap Metacello we need to change:
| > ConfigurationOfMetacello class >> bootstrapPackage: aString from:
| > aPath
| > | repository version |
| > repository := (MCCacheRepository uniqueInstance
| > includesVersionNamed: aString)
| > ifTrue: [MCCacheRepository uniqueInstance]
| > ifFalse: [MCHttpRepository
| > location: aPath
| > user: ''
| > password: ''].
| > repository
| > versionReaderForFileNamed: aString , '.mcz'
| > do: [:reader |
| > version := reader version.
| > version load.
| > version workingCopy repositoryGroup addRepository: repository]
| > I could commit, but I don't want to break Metacello loading in
| > other images and I don't know how do you handle these cases.
| > Thanks,
| > --
| > Mariano
| > http://marianopeck.wordpress.com