GLASS upgrade to #stable beta-9 loads #dev beta-9.1 instead

Hi Dale,

When I want to upgrade an extent that comes from GLASS 1.0-beta.8.7.4 to the stable GLASS 1.0-beta.9, it is the development version 1.0-beta.9.1 that gets loaded.
I tried via the 'upgrade GLASS' menu item, via a project reference with explicit version string in another configuration and 'manually' loading it with:

(ConfigurationOfGLASS project version: '1.0-beta.9')

I always end up getting the 9.1 version.
I do not get the problem if I use the one-but-last version of the configuration: ConfigurationOfGLASS-dkh.223

Johan

Johan,

I think this is a "problem" related to how Metacello calculates currentVersions .

Metacello starts at the latest version and works it's way backwards matching the spec for the version against the loaded image state. The only difference between 1.0-beta.9 and 1.0-beta.9.1 (at the moment) is that 1.0-beta.9.1 uses GsCore 0.248 instead of GsCore 0.247 and the only difference in GsCore 0.248 is that package Squeak.v3-dkh.297 is used instead of Squeak.v3-dkh.296 for gemstone 3.x ... which means that for 2.x 1.0-beta.9 and 1.0-beta.9.1 are identical and given the way the algorithm works, 1.0-beta.9.1 wins ...

I considered "fixing" the algorithm, but calculating the current version will always be a guessing game ... with the Metacello Scripting API, the system records the version that was loaded (using the original request) and the currentVersion calculation has been eliminated from code called via the API (`Metacello new....`). Loads using configuration as a target still use the old currentVersion algorithm (and one can force the old load algorithm to be used in the scripting api by using `Metacello classic...`).

I can create a new dummy version of Squeak-dkh.290 and record that in 1.0-beta.9.1 if that would help reduce the confusion.

Dale

----- Original Message -----
| From: "Johan Brichau" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Thursday, April 18, 2013 10:08:38 AM
| Subject: [GS/SS Beta] GLASS upgrade to #stable beta-9 loads #dev beta-9.1 instead
|
| Hi Dale,
|
| When I want to upgrade an extent that comes from GLASS 1.0-beta.8.7.4 to the
| stable GLASS 1.0-beta.9, it is the development version 1.0-beta.9.1 that
| gets loaded.
| I tried via the 'upgrade GLASS' menu item, via a project reference with
| explicit version string in another configuration and 'manually' loading it
| with:
|
| (ConfigurationOfGLASS project version: '1.0-beta.9')
|
| I always end up getting the 9.1 version.
| I do not get the problem if I use the one-but-last version of the
| configuration: ConfigurationOfGLASS-dkh.223
|
| Johan

Hi Dale,

It's not a display issue. GsCore 0.248 actually gets loaded although I explicitly ask for the beta.9 version

Johan

On 18 Apr 2013, at 20:37, Dale Henrichs <[hidden email]> wrote:

Johan,

Hmmm, I'd like to see the Transcript output for your run (it's accessible in the ObjectLog or the gem file if the load is done in topaz). The only explanation is that one of the other projects being loaded has an explicit dependency on GsCore 0.248 and I should be able to get an idea from the Transcript...

Dale

----- Original Message -----
| From: "Johan Brichau" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Thursday, April 18, 2013 12:39:41 PM
| Subject: Re: [GS/SS Beta] GLASS upgrade to #stable beta-9 loads #dev beta-9.1 instead
|
| Hi Dale,
|
| It's not a display issue. GsCore 0.248 actually gets loaded although I
| explicitly ask for the beta.9 version
|
| Johan
|
| On 18 Apr 2013, at 20:37, Dale Henrichs <[hidden email]> wrote:
|
| > Johan,
| >
| > I think this is a "problem" related to how Metacello calculates
| > currentVersions .
| >
| > Metacello starts at the latest version and works it's way backwards
| > matching the spec for the version against the loaded image state. The only
| > difference between 1.0-beta.9 and 1.0-beta.9.1 (at the moment) is that
| > 1.0-beta.9.1 uses GsCore 0.248 instead of GsCore 0.247 and the only
| > difference in GsCore 0.248 is that package Squeak.v3-dkh.297 is used
| > instead of Squeak.v3-dkh.296 for gemstone 3.x ... which means that for 2.x
| > 1.0-beta.9 and 1.0-beta.9.1 are identical and given the way the algorithm
| > works, 1.0-beta.9.1 wins ...
| >
| > I considered "fixing" the algorithm, but calculating the current version
| > will always be a guessing game ... with the Metacello Scripting API, the
| > system records the version that was loaded (using the original request)
| > and the currentVersion calculation has been eliminated from code called
| > via the API (`Metacello new....`). Loads using configuration as a target
| > still use the old currentVersion algorithm (and one can force the old load
| > algorithm to be used in the scripting api by using `Metacello
| > classic...`).
| >
| > I can create a new dummy version of Squeak-dkh.290 and record that in
| > 1.0-beta.9.1 if that would help reduce the confusion.
| >
| > Dale
| >
| > ----- Original Message -----
| > | From: "Johan Brichau" <[hidden email]>
| > | To: "GemStone Seaside beta discussion" <[hidden email]>
| > | Sent: Thursday, April 18, 2013 10:08:38 AM
| > | Subject: [GS/SS Beta] GLASS upgrade to #stable beta-9 loads #dev beta-9.1
| > | instead
| > |
| > | Hi Dale,
| > |
| > | When I want to upgrade an extent that comes from GLASS 1.0-beta.8.7.4 to
| > | the
| > | stable GLASS 1.0-beta.9, it is the development version 1.0-beta.9.1 that
| > | gets loaded.
| > | I tried via the 'upgrade GLASS' menu item, via a project reference with
| > | explicit version string in another configuration and 'manually' loading
| > | it
| > | with:
| > |
| > | (ConfigurationOfGLASS project version: '1.0-beta.9')
| > |
| > | I always end up getting the 9.1 version.
| > | I do not get the problem if I use the one-but-last version of the
| > | configuration: ConfigurationOfGLASS-dkh.223
| > |
| > | Johan
|
|