There are now two versions 40 in the repo.
The one I updated is copied to the metarepos,
so the problem is not yet fixed.
I only changed the catalog methods,
they need to be at the class side.
I don't know if you saw this post in pharo-dev?
On 19-06-15 07:11, Alejandro Infante wrote:
I did that because when using:
smalltalkhubUser: 'ObjectProfile' project: 'Roassal2';
It was installing 1.52 even though the stable version of Roassal was 1.12.
Instead if I used:
Gofer new smalltalkhubUser: 'ObjectProfile'
((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load
I was getting the right version (1.12).
Gofer>>loadStable does not use the
(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.
B.t.w. I'm not quite sure why there is an old ConfigurationOfGlamourCore
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.