Loading latest Magritte fails, understanding MC
renggli at iam.unibe.ch
Tue Jun 13 00:42:53 MEST 2006
> MessageNotUnderstood: MACachedBuilder>>modified:
> When loading Magritte-Model-lr.219.mcz ...
Some versions I publish break backward compatibility, even-tough I
try to avoid that as much as possible. If there is no other clean way
to do it, then I usually give detailled instructions in the mailing
list how to migrate:
See the following URL for your particular problem:
> Also, coming from the CVS/SVN kind of version control systems, I'm
> quite troubled by MC...
> - Is there a specific order to load package versions ?
For my projects it is always the same: model first, view next, and at
last the tests. So for Magritte the order would be: Magritte-Model,
Magritte-Seaside, Magritte-Morph, Magritte-Tests.
> - are there dependancies between versions ?
Yes, but Monticello is not really able to model that. See the
dependencies of the empty package Magritte-All for snapshot from my
image. Usually it is a good practice to simply load the latest
versions, or maybe in your case load the version from SqueakMap.
> - what is the equivalent of apt-get update && apt-get -f dist-
> upgrade ?
Sorry, I only know "emerge sync && emerge -uD world" ;-)
More information about the SmallWiki