At 8:22 PM -0800 2/14/10, Colin Putney apparently wrote:
>On 2010-02-12, at 11:17 PM, Andreas Raab wrote:
>
>> Hi Colin -
>>
>> In your newly found role as MC maintainer, I have a question for you: I am wondering about the role of errorDefinitions in MCPackageLoader. What errors are they supposed to capture? The only one I am aware of is when a variable gets moved up or down inside a package. Are there others?
>>
>> (the reason I'm asking is that I fixed this case today with help from Eliot, so we may be able to remove this unnecessary complexity)
>
>I don't think this was meant a workaround to a known problem. It's just a way to gracefully handle unexpected errors while loading a package.
>
>I'm setting up a new repository for MC1 development, where we can collect the history relevant to the current trunk version, and commit fixes and further development. I figure the best way to distribute is just to push to the trunk repository, but we'll at least have well-defined releases. Is the fix you and Eliot made available somewhere?
>
>Colin

There already is an established repo at <http://www.squeaksource.com/mc.html> which gathered together all the previous state of the art of MC before trunk and Pharo continued their divergent MC paths on the ancient version.

See also:
Matthew Fulmer's 'place for me to keep the scattered info on monticello versions 1.5 and 1.6 until it has a proper home and is released'

<http://installer.pbworks.com/Monticello15>

Ken G. Brown