Why not put a version of the config in the Pharo40Metarepo and leave it at that?

As the new stuff occurs in Pharo5, new configs should go in a Pharo50Metarepo and not affect anything in 4.0

Feeback welcome.

Phil

On Wed, Sep 30, 2015 at 10:57 AM, Volkert <volkert@komponentenwerkstatt.de> wrote:
Now is fine again ... :-)

... i will try to understand how Configuration stuff works. Will first read "Deep into Pharo" today ...

BW,
Volkert

On 30.09.2015 10:45, Alexandre Bergel wrote:
Sorry guys for this regression.
I have reverted the configuration. It is really mysterious how it works.

So, in summary, to load Roassal on Pharo 4 you need to do:
        Gofer it
                smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
                configurationOf: 'Roassal2';
                loadVersion: '1.15'.

Cheers,
Alexandre



On Sep 30, 2015, at 9:15 AM, phil@highoctane.be wrote:

Same here.

On Wed, Sep 30, 2015 at 7:38 AM, Volkert <volkert@komponentenwerkstatt.de> wrote:
Now version 1.15 produce the warning as well :-(


<begfacfh.png>



On 28.09.2015 20:43, Alexandre Bergel wrote:
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

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


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

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