Hi Miguel. I understand your problem, and we are working on that with Dale and Stef. Having repositories for a specific Pharo version and so on. But we are just starting....

By the moment, you can use what Sean told you, or, just update the configuration, but in a new version. I mean....if you had the version 2.3.4 that was released and working in pharo 1.0, then don't touch it, create a new one, say, 2.4 and that works in 1.1. Of course this is not the perfect solution, but for the moment. But one thing for sure: do not update the SAME version that was working for 1.0.
Magma should continue working in 1.0 using the same metacello version.

cheers

mariano

On Tue, Jul 20, 2010 at 9:26 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:

For now, you can use the hack that Dale suggested in
http://groups.google.com/group/metacello/browse_thread/thread/a27c95d24974adda/31fdfa02fc18a4e3.

> Take a look a ConfigurationOfGemTools>>project. In that method I created a
> #'pharo1.0Beta' attribute by looking at the SystemVersion current
> version...
--
View this message in context: http://forum.world.st/ANN-ConfigurationOfMagma-for-Magma-1-1r1-tp2242566p2295046.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project