Pharo 4 and Roassal
Locked
 
|
Hi
I recently tried experimenting with Pharo and Roassal and I found some problems, so I would like to know how to load Roassal in pharo 4 to retry everything from scratch and also see if the problems are due to some other cause. best regards JMDC |
|
|
Hi, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadDevelopment ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you also want GTInspector presenters, then also run ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-InspectorExtensions-CoreRoassal'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'Glamour-Tools'; package: 'Glamour-Roassal2-Presentations'; load. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ But it is better to say what problems have you ran into. Peter On Thu, Jun 18, 2015 at 9:02 PM, Juan <[hidden email]> wrote:
|
|
|
In reply to this post by Juan-2
Hi Juan,
Rubric has changed its configuration. Apparently they removed a version, which is a very bad practice. Well… Things are broken now… Alexandre > On Jun 18, 2015, at 4:02 PM, Juan <[hidden email]> wrote: > > Hi > > I recently tried experimenting with Pharo and Roassal and I found some problems, so I would like to know how to load Roassal in pharo 4 to retry everything from scratch and also see if the problems are due to some other cause. > > best regards > > JMDC -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
|
|
In reply to this post by Juan-2
Juan,
I have just tried loading Roassal on Pharo5 and it works well. I have the catalog browser and installed it. All went smoothly. You can download Pharo 5 from the Pharo.org website. Cheers, Alexandre > On Jun 18, 2015, at 4:02 PM, Juan <[hidden email]> wrote: > > Hi > > I recently tried experimenting with Pharo and Roassal and I found some problems, so I would like to know how to load Roassal in pharo 4 to retry everything from scratch and also see if the problems are due to some other cause. > > best regards > > JMDC -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
|
|
In reply to this post by abergel
> Hi Juan, > > Rubric has changed its configuration. Apparently they removed a version, which is a very bad practice. Well… Things are broken now… Where? Because I do not see how a version can be removed. So may be the configuration you rely one is simply not defined to be dependent on? Stef > > Alexandre > > >> On Jun 18, 2015, at 4:02 PM, Juan <[hidden email]> wrote: >> >> Hi >> >> I recently tried experimenting with Pharo and Roassal and I found some problems, so I would like to know how to load Roassal in pharo 4 to retry everything from scratch and also see if the problems are due to some other cause. >> >> best regards >> >> JMDC |
|
|
Because I do not see how a version can be removed. Configuration is version-less so if you can remove it there, or just change it... e.g. ~~~~~ Name: ConfigurationOfRoassal2-AlejandroInfante.37 Author: AlejandroInfante Time: 2 June 2015, 6:48:30.901514 pm UUID: 6257332e-2902-4cd0-ba0f-0d9180ac6e65 Ancestors: ConfigurationOfRoassal2-AlejandroInfante.36 Fixed version 1.51 and 1.52 to be 1.5.1 and 1.5.2. ~~~~ Not sure if it is good approach, but even in git you can remove tags/versions and rewrite history, but if you know about it it's rarely a problem. Peter |
|
|
Hi,
I did that because when using: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It was installing 1.52 even though the stable version of Roassal was 1.12. Instead if I used: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I was getting the right version (1.12). Then looking the commit numbers loaded in 1.51 I realized that it was 1.5.1, but was never fixed and fixing it solves the problem. I was hoping to do more experiments before reporting it to the mailing list, but I was in a hurry because Roassal was being loaded incorrectly for everyone that tried to load the stable version in a Pharo4.0 image. About the people that was relying of 1.51 and 1.52 version name, I’m deeply apologized for the troubles I may have caused, but the Roassal versions were inconsistently defined and I did not found any way to solve that cleanly. Even though I do not know how this can affect the loading of Roassal stable version now (that was 2 weeks ago) and considering that Roassal does not depends directly on Rubric. Cheers, Alejandro PS: I would appreciate if someone can point a better way to handle the issue with version 1.51 and 1.52 of Roassal2 and hope nobody face any problem with it, because we have not received any complains about it (yet).
|
|
|
Hi, About the current problem, I have found that Roassal2 current stable version depends on GlamourCore version 3.1.4, which depends on Rubric version 1.2.14 (the actual version that Metacello can’t find) which use 3.1-baseline. Indeed this version is not visible from ConfigurationOfGlamourCore>>3.1-baseline (http://www.smalltalkhub.com/mc/AlainPlantec/Rubric/main), but it is visible from ConfigurationOfGlamourCore>>3.2-baseline (http://www.smalltalkhub.com/mc/Pharo/Rubric/main) So I don’t know if it is better to change GlamourCore version 3.1.4 to use 3.2-baseline (and change the history) or create a new version that use the new baseline, which involves to change all the projects that depends on version 3.1.4 of GlamourCore. Also I do not own the configuration of GlamourCore and I don’t know either about Glamour dependencies, so I will not touch it. But this information should be useful to someone who knows about Glamour. Cheers, Alejandro
|
|
|
In reply to this post by Alejandro Infante
On 19-06-15 07:11, Alejandro Infante wrote:
> Hi, > I did that because when using: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; > loadStable > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > It was installing 1.52 even though the stable version of Roassal was 1.12. > Instead if I used: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer new smalltalkhubUser: 'ObjectProfile' > project: 'Roassal2'; > package: 'ConfigurationOfRoassal2'; > load. > ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > I was getting the right version (1.12). Gofer>>loadStable does not use the ConfigurationOfRoassal2 class>>loadStable (which is undefined, but many configurations define as self project load: #stable but loadVersion: #stable, which uses the latest version marked #stable. So yes, that is something you'd want to fix in place. And warn about on the mailing list. In this version 1.12 then we see that Roassal is tightly coupled to an old version of GlamourCore. So either ConfigurationOfRoassal2 needs to add a new #stable version every time GlamourCore #stable for Pharo 4 is updated, or it should depend on GlamourCore #stable. And ConfigurationOfGlamourCore has actually the same problem, as #stable currently depends on an old version of Rubric. So that should have been one or two versions more. And please note that this is for the released Pharo 4, where we are only supposed to backport important fixes. I strongly suggest to make ConfigurationOfGlamourCore #stable depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. Depending on #stable instead of #release1 or so works out ok here as long there is not supposed to be a new release for Pharo 4. Stephan |
|
|
Alejandro,
I do not remember why Roassal depends on Glamour? I guess this is because of the GTInspector? Alexandre > On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: > > On 19-06-15 07:11, Alejandro Infante wrote: >> Hi, >> I did that because when using: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Gofer it >> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >> configurationOf: 'Roassal2'; >> loadStable >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> It was installing 1.52 even though the stable version of Roassal was 1.12. >> Instead if I used: >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Gofer new smalltalkhubUser: 'ObjectProfile' >> project: 'Roassal2'; >> package: 'ConfigurationOfRoassal2'; >> load. >> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> I was getting the right version (1.12). > > Gofer>>loadStable does not use the > > ConfigurationOfRoassal2 class>>loadStable > > (which is undefined, but many configurations define as > > self project load: #stable > > but loadVersion: #stable, which uses the latest version marked #stable. > > So yes, that is something you'd want to fix in place. > And warn about on the mailing list. > > In this version 1.12 then we see that Roassal is tightly coupled to > an old version of GlamourCore. So either ConfigurationOfRoassal2 > needs to add a new #stable version every time GlamourCore #stable > for Pharo 4 is updated, or it should depend on GlamourCore #stable. > And ConfigurationOfGlamourCore has actually the same problem, as > #stable currently depends on an old version of Rubric. So that > should have been one or two versions more. And please note that > this is for the released Pharo 4, where we are only supposed to > backport important fixes. > > I strongly suggest to make ConfigurationOfGlamourCore #stable > depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. > > Depending on #stable instead of #release1 or so works out ok > here as long there is not supposed to be a new release for Pharo 4. > > Stephan > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
|
|
Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples.
Alejandro > On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <[hidden email]> wrote: > > Alejandro, > > I do not remember why Roassal depends on Glamour? > I guess this is because of the GTInspector? > > Alexandre > >> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >> >> On 19-06-15 07:11, Alejandro Infante wrote: >>> Hi, >>> I did that because when using: >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Gofer it >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> configurationOf: 'Roassal2'; >>> loadStable >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>> Instead if I used: >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Gofer new smalltalkhubUser: 'ObjectProfile' >>> project: 'Roassal2'; >>> package: 'ConfigurationOfRoassal2'; >>> load. >>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> I was getting the right version (1.12). >> >> Gofer>>loadStable does not use the >> >> ConfigurationOfRoassal2 class>>loadStable >> >> (which is undefined, but many configurations define as >> >> self project load: #stable >> >> but loadVersion: #stable, which uses the latest version marked #stable. >> >> So yes, that is something you'd want to fix in place. >> And warn about on the mailing list. >> >> In this version 1.12 then we see that Roassal is tightly coupled to >> an old version of GlamourCore. So either ConfigurationOfRoassal2 >> needs to add a new #stable version every time GlamourCore #stable >> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >> And ConfigurationOfGlamourCore has actually the same problem, as >> #stable currently depends on an old version of Rubric. So that >> should have been one or two versions more. And please note that >> this is for the released Pharo 4, where we are only supposed to >> backport important fixes. >> >> I strongly suggest to make ConfigurationOfGlamourCore #stable >> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >> >> Depending on #stable instead of #release1 or so works out ok >> here as long there is not supposed to be a new release for Pharo 4. >> >> Stephan >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > |
|
|
I think this is because the latest glamour core was not in the base image… I do not remember exactly.
Alexandre > On Jun 20, 2015, at 10:25 PM, Alejandro Infante <[hidden email]> wrote: > > Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples. > > Alejandro > >> On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <[hidden email]> wrote: >> >> Alejandro, >> >> I do not remember why Roassal depends on Glamour? >> I guess this is because of the GTInspector? >> >> Alexandre >> >>> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >>> >>> On 19-06-15 07:11, Alejandro Infante wrote: >>>> Hi, >>>> I did that because when using: >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> Gofer it >>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>> configurationOf: 'Roassal2'; >>>> loadStable >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>>> Instead if I used: >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> Gofer new smalltalkhubUser: 'ObjectProfile' >>>> project: 'Roassal2'; >>>> package: 'ConfigurationOfRoassal2'; >>>> load. >>>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> I was getting the right version (1.12). >>> >>> Gofer>>loadStable does not use the >>> >>> ConfigurationOfRoassal2 class>>loadStable >>> >>> (which is undefined, but many configurations define as >>> >>> self project load: #stable >>> >>> but loadVersion: #stable, which uses the latest version marked #stable. >>> >>> So yes, that is something you'd want to fix in place. >>> And warn about on the mailing list. >>> >>> In this version 1.12 then we see that Roassal is tightly coupled to >>> an old version of GlamourCore. So either ConfigurationOfRoassal2 >>> needs to add a new #stable version every time GlamourCore #stable >>> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >>> And ConfigurationOfGlamourCore has actually the same problem, as >>> #stable currently depends on an old version of Rubric. So that >>> should have been one or two versions more. And please note that >>> this is for the released Pharo 4, where we are only supposed to >>> backport important fixes. >>> >>> I strongly suggest to make ConfigurationOfGlamourCore #stable >>> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >>> >>> Depending on #stable instead of #release1 or so works out ok >>> here as long there is not supposed to be a new release for Pharo 4. >>> >>> Stephan >>> >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
|
|
It is loaded in Pharo4, but in order to verify that it is up to date, Metacello needs to check the ConfigurationOf for the required version and that fails.
Alejandro > On Jun 20, 2015, at 10:29 PM, Alexandre Bergel <[hidden email]> wrote: > > I think this is because the latest glamour core was not in the base image… I do not remember exactly. > > Alexandre > > >> On Jun 20, 2015, at 10:25 PM, Alejandro Infante <[hidden email]> wrote: >> >> Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples. >> >> Alejandro >> >>> On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <[hidden email]> wrote: >>> >>> Alejandro, >>> >>> I do not remember why Roassal depends on Glamour? >>> I guess this is because of the GTInspector? >>> >>> Alexandre >>> >>>> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >>>> >>>> On 19-06-15 07:11, Alejandro Infante wrote: >>>>> Hi, >>>>> I did that because when using: >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> Gofer it >>>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>>> configurationOf: 'Roassal2'; >>>>> loadStable >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>>>> Instead if I used: >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> Gofer new smalltalkhubUser: 'ObjectProfile' >>>>> project: 'Roassal2'; >>>>> package: 'ConfigurationOfRoassal2'; >>>>> load. >>>>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> I was getting the right version (1.12). >>>> >>>> Gofer>>loadStable does not use the >>>> >>>> ConfigurationOfRoassal2 class>>loadStable >>>> >>>> (which is undefined, but many configurations define as >>>> >>>> self project load: #stable >>>> >>>> but loadVersion: #stable, which uses the latest version marked #stable. >>>> >>>> So yes, that is something you'd want to fix in place. >>>> And warn about on the mailing list. >>>> >>>> In this version 1.12 then we see that Roassal is tightly coupled to >>>> an old version of GlamourCore. So either ConfigurationOfRoassal2 >>>> needs to add a new #stable version every time GlamourCore #stable >>>> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >>>> And ConfigurationOfGlamourCore has actually the same problem, as >>>> #stable currently depends on an old version of Rubric. So that >>>> should have been one or two versions more. And please note that >>>> this is for the released Pharo 4, where we are only supposed to >>>> backport important fixes. >>>> >>>> I strongly suggest to make ConfigurationOfGlamourCore #stable >>>> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >>>> >>>> Depending on #stable instead of #release1 or so works out ok >>>> here as long there is not supposed to be a new release for Pharo 4. >>>> >>>> Stephan >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > |
|
|
I have changed the blessing of Roassal2 version 1.12 and 1.13 to #broken, so now you will install by default version 1.11 that works out of the box in Pharo4.
I have just tested this so feel free to ask us if you have any problems. We will restore the blessing of 1.12 and 1.13 to #stable when ConficurationOfGlamourCore is fixed. Cheers, Alejandro > On Jun 20, 2015, at 11:05 PM, Alejandro Infante <[hidden email]> wrote: > > It is loaded in Pharo4, but in order to verify that it is up to date, Metacello needs to check the ConfigurationOf for the required version and that fails. > > Alejandro > >> On Jun 20, 2015, at 10:29 PM, Alexandre Bergel <[hidden email]> wrote: >> >> I think this is because the latest glamour core was not in the base image… I do not remember exactly. >> >> Alexandre >> >> >>> On Jun 20, 2015, at 10:25 PM, Alejandro Infante <[hidden email]> wrote: >>> >>> Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples. >>> >>> Alejandro >>> >>>> On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <[hidden email]> wrote: >>>> >>>> Alejandro, >>>> >>>> I do not remember why Roassal depends on Glamour? >>>> I guess this is because of the GTInspector? >>>> >>>> Alexandre >>>> >>>>> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >>>>> >>>>> On 19-06-15 07:11, Alejandro Infante wrote: >>>>>> Hi, >>>>>> I did that because when using: >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> Gofer it >>>>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>>>> configurationOf: 'Roassal2'; >>>>>> loadStable >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>>>>> Instead if I used: >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> Gofer new smalltalkhubUser: 'ObjectProfile' >>>>>> project: 'Roassal2'; >>>>>> package: 'ConfigurationOfRoassal2'; >>>>>> load. >>>>>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>>> I was getting the right version (1.12). >>>>> >>>>> Gofer>>loadStable does not use the >>>>> >>>>> ConfigurationOfRoassal2 class>>loadStable >>>>> >>>>> (which is undefined, but many configurations define as >>>>> >>>>> self project load: #stable >>>>> >>>>> but loadVersion: #stable, which uses the latest version marked #stable. >>>>> >>>>> So yes, that is something you'd want to fix in place. >>>>> And warn about on the mailing list. >>>>> >>>>> In this version 1.12 then we see that Roassal is tightly coupled to >>>>> an old version of GlamourCore. So either ConfigurationOfRoassal2 >>>>> needs to add a new #stable version every time GlamourCore #stable >>>>> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >>>>> And ConfigurationOfGlamourCore has actually the same problem, as >>>>> #stable currently depends on an old version of Rubric. So that >>>>> should have been one or two versions more. And please note that >>>>> this is for the released Pharo 4, where we are only supposed to >>>>> backport important fixes. >>>>> >>>>> I strongly suggest to make ConfigurationOfGlamourCore #stable >>>>> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >>>>> >>>>> Depending on #stable instead of #release1 or so works out ok >>>>> here as long there is not supposed to be a new release for Pharo 4. >>>>> >>>>> Stephan >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > |
|
|
In reply to this post by abergel
Le 21/6/15 03:22, Alexandre Bergel a écrit : > Alejandro, > > I do not remember why Roassal depends on Glamour? > I guess this is because of the GTInspector? and this is a bad idea. You should have a package Roassal-GT that is different from Roassal-Core. Stef > > Alexandre > >> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >> >> On 19-06-15 07:11, Alejandro Infante wrote: >>> Hi, >>> I did that because when using: >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Gofer it >>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>> configurationOf: 'Roassal2'; >>> loadStable >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>> Instead if I used: >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> Gofer new smalltalkhubUser: 'ObjectProfile' >>> project: 'Roassal2'; >>> package: 'ConfigurationOfRoassal2'; >>> load. >>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> I was getting the right version (1.12). >> Gofer>>loadStable does not use the >> >> ConfigurationOfRoassal2 class>>loadStable >> >> (which is undefined, but many configurations define as >> >> self project load: #stable >> >> but loadVersion: #stable, which uses the latest version marked #stable. >> >> So yes, that is something you'd want to fix in place. >> And warn about on the mailing list. >> >> In this version 1.12 then we see that Roassal is tightly coupled to >> an old version of GlamourCore. So either ConfigurationOfRoassal2 >> needs to add a new #stable version every time GlamourCore #stable >> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >> And ConfigurationOfGlamourCore has actually the same problem, as >> #stable currently depends on an old version of Rubric. So that >> should have been one or two versions more. And please note that >> this is for the released Pharo 4, where we are only supposed to >> backport important fixes. >> >> I strongly suggest to make ConfigurationOfGlamourCore #stable >> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >> >> Depending on #stable instead of #release1 or so works out ok >> here as long there is not supposed to be a new release for Pharo 4. >> >> Stephan >> >> >> >> >> |
|
|
In reply to this post by abergel
But even if package gets "used" and loaded in the image. We are going to
use configuration everywhere. So you should start to really use them and do not put everything in one package :) Stef Le 21/6/15 03:29, Alexandre Bergel a écrit : > I think this is because the latest glamour core was not in the base image… I do not remember exactly. > > Alexandre > > >> On Jun 20, 2015, at 10:25 PM, Alejandro Infante <[hidden email]> wrote: >> >> Exactly, all the customized views are dependent of GlamourCore and also the Easel depends on Glamour for showing the examples. >> >> Alejandro >> >>> On Jun 20, 2015, at 10:22 PM, Alexandre Bergel <[hidden email]> wrote: >>> >>> Alejandro, >>> >>> I do not remember why Roassal depends on Glamour? >>> I guess this is because of the GTInspector? >>> >>> Alexandre >>> >>>> On Jun 19, 2015, at 8:11 AM, Stephan Eggermont <[hidden email]> wrote: >>>> >>>> On 19-06-15 07:11, Alejandro Infante wrote: >>>>> Hi, >>>>> I did that because when using: >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> Gofer it >>>>> smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; >>>>> configurationOf: 'Roassal2'; >>>>> loadStable >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> It was installing 1.52 even though the stable version of Roassal was 1.12. >>>>> Instead if I used: >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> Gofer new smalltalkhubUser: 'ObjectProfile' >>>>> project: 'Roassal2'; >>>>> package: 'ConfigurationOfRoassal2'; >>>>> load. >>>>> ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load >>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>>> I was getting the right version (1.12). >>>> Gofer>>loadStable does not use the >>>> >>>> ConfigurationOfRoassal2 class>>loadStable >>>> >>>> (which is undefined, but many configurations define as >>>> >>>> self project load: #stable >>>> >>>> but loadVersion: #stable, which uses the latest version marked #stable. >>>> >>>> So yes, that is something you'd want to fix in place. >>>> And warn about on the mailing list. >>>> >>>> In this version 1.12 then we see that Roassal is tightly coupled to >>>> an old version of GlamourCore. So either ConfigurationOfRoassal2 >>>> needs to add a new #stable version every time GlamourCore #stable >>>> for Pharo 4 is updated, or it should depend on GlamourCore #stable. >>>> And ConfigurationOfGlamourCore has actually the same problem, as >>>> #stable currently depends on an old version of Rubric. So that >>>> should have been one or two versions more. And please note that >>>> this is for the released Pharo 4, where we are only supposed to >>>> backport important fixes. >>>> >>>> I strongly suggest to make ConfigurationOfGlamourCore #stable >>>> depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. >>>> >>>> Depending on #stable instead of #release1 or so works out ok >>>> here as long there is not supposed to be a new release for Pharo 4. >>>> >>>> Stephan >>>> >>>> >>>> >>>> >>>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |