Yeah, it would be great to have this behavior. But no idea how.
I tried to have in ConfigurationOfRoassal2:
stable: spec <symbolicVersion: #'stable'>
spec for: #'common' version: '1.16'. spec for: #'pharo4.x' version: '1.15'. spec for: #'pharo3.x' version: '1.6'. spec for: #'pharo5.x' version: '1.16’.
But loading: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable
in pharo 4 still produces the error.
Alexandre
On Sep 25, 2015, at 7:52 AM, Sven Van Caekenberghe sven@stfx.eu wrote:
On 25 Sep 2015, at 05:18, Volkert volkert@komponentenwerkstatt.de wrote:
But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.
You are right, as an end user you should just use #stable on any supported platform and it should work.
The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.
Obviously someone made a mistake while moving forward, we are all humans after all. _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev