GToolkit loading problem

Hi, 

I try to load GT tools to minimal Pharo image (with Morphic) and I have problems to do that because it has a dependency cycle it these methods:

  GLMBrickDarkThemer>>#actionThemer

  GLMBrickThemer>>#actionThemer

These methods try to extend classes in Glamour-Morphic-Brick package but they belong to Glamour-Core package that is prerequisite of the first package. 

The image without GT tools for testing is hrere: https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

Cheers,

-- Pavel

Hi Pavel,

I fixed the issue in the glamour repo and updated the configurations.

Still I get the same error when trying to load ConfigurationOfGToolkit #stable into PharoIDE, as monticello

seems to not resolve versions correctly.

To reproduce first update all configurations:

{       { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.

        { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.

        { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.

{ 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.

} do: [ :spec |

        Gofer new

                smalltalkhubUser: spec second project: spec third;

                package: spec first;

                load ].

Then print:

(ConfigurationOfGToolkitCore project version: #stable) record loadDirective

ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it should be 3.0.4

Now ConfigurationOfGToolkitCore>>#stable is defined as

ConfigurationOfGToolkitCore >>stable: spec

<symbolicVersion: #'stable'>

spec for: #'common' version: '3.0.4'.

spec for: #'pharo4.x' version: '3.0.2'.

If I add an entry for pharo5.x then it works.

Through I think it should also work without one.

Cheers,

Andrei

On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek <[hidden email]> wrote:

Hi, 

I try to load GT tools to minimal Pharo image (with Morphic) and I have problems to do that because it has a dependency cycle it these methods:

  GLMBrickDarkThemer>>#actionThemer

  GLMBrickThemer>>#actionThemer

These methods try to extend classes in Glamour-Morphic-Brick package but they belong to Glamour-Core package that is prerequisite of the first package. 

The image without GT tools for testing is hrere: https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

Cheers,

-- Pavel

On 03 Jul 2015, at 16:42, Andrei Chis <[hidden email]> wrote:

On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek <[hidden email]> wrote:

Hi, 

thank you, Andrei.

SmalltalkImage>>#metacelloPlatformAttributes are defined currently as (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x') for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over 'common'.

Ahaaa.

Then I kind of misunderstood how platform attributes work.

I need now to update some configurations from GTools.

but this is an error. 

#metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon #pharo #'pharo5.x' #'pharo5.0.x’)

then your configuration should be taking #common and not #pharo4.x

cheers, 

Esteban

Cheers,

Andrei

 

Cheers,

-- Pavel 

2015-07-03 14:37 GMT+02:00 Andrei Chis <[hidden email]>:

Hi Pavel,

I fixed the issue in the glamour repo and updated the configurations.

Still I get the same error when trying to load ConfigurationOfGToolkit #stable into PharoIDE, as monticello

seems to not resolve versions correctly.

To reproduce first update all configurations:

{       { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.

        { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.

        { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.

{ 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.

} do: [ :spec |

        Gofer new

                smalltalkhubUser: spec second project: spec third;

                package: spec first;

                load ].

Then print:

(ConfigurationOfGToolkitCore project version: #stable) record loadDirective

ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it should be 3.0.4

Now ConfigurationOfGToolkitCore>>#stable is defined as

ConfigurationOfGToolkitCore >>stable: spec

<symbolicVersion: #'stable'>

spec for: #'common' version: '3.0.4'.

spec for: #'pharo4.x' version: '3.0.2'.

If I add an entry for pharo5.x then it works.

Through I think it should also work without one.

Cheers,

Andrei

On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek <[hidden email]> wrote:

Hi, 

I try to load GT tools to minimal Pharo image (with Morphic) and I have problems to do that because it has a dependency cycle it these methods:

  GLMBrickDarkThemer>>#actionThemer

  GLMBrickThemer>>#actionThemer

These methods try to extend classes in Glamour-Morphic-Brick package but they belong to Glamour-Core package that is prerequisite of the first package. 

The image without GT tools for testing is hrere: https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

Cheers,

-- Pavel

you need to create one :P

On 08 Jul 2015, at 11:47, Andrei Chis <[hidden email]> wrote:

Is there bug report for this or should I create one?

cheers,

Andrei

On Fri, Jul 3, 2015 at 4:58 PM, Esteban Lorenzano <[hidden email]> wrote:

On 03 Jul 2015, at 16:42, Andrei Chis <[hidden email]> wrote:

On Fri, Jul 3, 2015 at 3:37 PM, Pavel Krivanek <[hidden email]> wrote:

Hi, 

thank you, Andrei.

SmalltalkImage>>#metacelloPlatformAttributes are defined currently as (#squeakCommon #pharo #'pharo4.x' #'pharo4.0.x' #'pharo5.x' #'pharo5.0.x') for Pharo 5 (from most to least general) so it will prefer 'pharo4.x' over 'common'.

Ahaaa.

Then I kind of misunderstood how platform attributes work.

I need now to update some configurations from GTools.

but this is an error. 

#metacelloPlatformAttributes for Pharo 5 should be: #(#squeakCommon #pharo #'pharo5.x' #'pharo5.0.x’)

then your configuration should be taking #common and not #pharo4.x

cheers, 

Esteban

Cheers,

Andrei

 

Cheers,

-- Pavel 

2015-07-03 14:37 GMT+02:00 Andrei Chis <[hidden email]>:

Hi Pavel,

I fixed the issue in the glamour repo and updated the configurations.

Still I get the same error when trying to load ConfigurationOfGToolkit #stable into PharoIDE, as monticello

seems to not resolve versions correctly.

To reproduce first update all configurations:

{       { 'ConfigurationOfRubric'. 'Pharo'. 'Rubric' }.

        { 'ConfigurationOfGlamourCore'. 'Moose'. 'Glamour' }.

        { 'ConfigurationOfGTInspectorCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTPlaygroundCore'. 'Moose'. 'GToolkit' }.

        { 'ConfigurationOfGTSpotter'. 'Moose'. 'GToolkit' }.

{ 'ConfigurationOfGToolkitCore'. 'Moose'. 'GToolkit' }.

} do: [ :spec |

        Gofer new

                smalltalkhubUser: spec second project: spec third;

                package: spec first;

                load ].

Then print:

(ConfigurationOfGToolkitCore project version: #stable) record loadDirective

ConfigurationOfGToolkitCore is resolved to version 3.0.2 even though it should be 3.0.4

Now ConfigurationOfGToolkitCore>>#stable is defined as

ConfigurationOfGToolkitCore >>stable: spec

<symbolicVersion: #'stable'>

spec for: #'common' version: '3.0.4'.

spec for: #'pharo4.x' version: '3.0.2'.

If I add an entry for pharo5.x then it works.

Through I think it should also work without one.

Cheers,

Andrei

On Fri, Jul 3, 2015 at 1:09 PM, Pavel Krivanek <[hidden email]> wrote:

Hi, 

I try to load GT tools to minimal Pharo image (with Morphic) and I have problems to do that because it has a dependency cycle it these methods:

  GLMBrickDarkThemer>>#actionThemer

  GLMBrickThemer>>#actionThemer

These methods try to extend classes in Glamour-Morphic-Brick package but they belong to Glamour-Core package that is prerequisite of the first package. 

The image without GT tools for testing is hrere: https://ci.inria.fr/pharo/view/5.0-SysConf/job/Pharo-5.0-ConfigurationOfIDE/

Cheers,

-- Pavel