On Mon, Dec 5, 2011 at 8:22 AM, jtuchel <jtuchel@objektfabrik.de> wrote:
Hi Mariano,

thanks a lot for your tip. So it seems like method
ConfigurationOfMaClientServer>>#version13: needs to be updated. It loads
V4.4.0 of OSProcess.

spec
                       project: 'MaBase' with: '1.0';
                       project: 'OSProcess' with: '4.4.0'.

So there is the next question: A look at ConfigurationOfOSProcess reveals
that version440 loads package OSProcess-dtl.59 , as of today, the latest
version on squeak source is OSProcess-dtl.66.mcz.

How can I find out which one between 59 and 66 is the right one? Or maybe I

Only their developers know.
 
shouldn't worry about it, but look at ConfigurationOfOSProcess instead...
But searching for ConfigurationOfOSProcess on Squeaksource doesn't bring up
any results.


The problem is so well know that we should find a name for it.....
it is simple: the guys who do the project, do not do/maintain the Metacello configurations.
 
So should I be using the MonticelloBrowser to look at
MetacelloRepository?


Yes, you can.
 
I tried it on http:://www.squeaksource.com/MetacelloRepository and
surprisingly found out that I have the very latest version of
ConfigurationOfOSProcess loaded: ConfigurationOfOSProcess-mt.17

So it seems both ConfigurationOfOSProcess and
ConfigurationOfMagmaClientServer (and therefor I guess all dependent
configurations) need an update...


Welcome to the real world: nobody updates the configurations. Not even when the load doesn't work.
In the case of Magma and OSProcess nor of their developers did/maintain the configurations. I am not saying they shuld. everybody do as much as they can/want, I am just explaining you why it has not been updated.
 
Coming from Envy I find this whole Metacello stuff both a big improvement
over Monticello and a bit low level. But maybe the last one is just a
question of re-educating myself ;-)

From my point of view, the problem is not the tool, but how people use it.
 
Still I am a bit puzzled about what I could do to make Magma load cleanly
into Pharo 1.3, other than fixing that one line in the debugger on every
load. Being an envy user, seeing a debugger during load leaves a bit of a
bitter taste in my throat, because chances are you are going to face
problems that stem from the broken atomicity of a load...

yes...
 

But most of all: thanks for the pointers. I have learned a bit more about
Metacello today, which is a good thing!

Read the chapter if you want to know more about the tool itself :)
 

Joachim



--
View this message in context: http://forum.world.st/Re-Pharo-users-pharo-users-Can-t-Load-Magma-in-Pharo-1-3-tp3933449p4159515.html
Sent from the Magma mailing list archive at Nabble.com.
_______________________________________________
Magma mailing list
Magma@lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/magma



--
Mariano
http://marianopeck.wordpress.com