Sorry but this has nothing to do with Pharo.
We migrated Moose (150 packages) from pharo 30 to 40 in two days.
So pharo is not unstable!
Repeat after me Pharo is not unstable.

Now if people do not maintain Roassal2 to load in several versions of Pharo this is the
fault of Pharo.

When my mac backup tool does not work on yosemite anymore I do not say that this is an objective-C problem.

Stef

PS: why don't you try to find the latest version of Roassal that worked in Pharo40 and make sure that you use this one.

Roassal2 (stable) does not load into Pharo 4.0 anymore:-(

Too bad that Pharo is so instable ...

Volkert
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev