[Seaside] Setup Pier environment

Dale Henrichs dale.henrichs at gemtalksystems.com
Thu Oct 23 18:27:54 UTC 2014


The #currentVersion algorithm does a match between the packages loaded and
the specifications and the match is based on "latest version matching" and
this is an inexact science (as you've seen) ... Most likely in the case you
are wondering about, the gemstone packges are identical between version
3.0.4 and 3.1.1 so the #currentVersion algorithm matches 3.1.1.

You've probably seen that these days I recommend using the scripting api
where you would do
the load this way:

  Metacello new
    configuration: 'Pier3AddOns';
    version: '3.0.4';

then print the following to check which version has been loaded:

  Metacello image
    configuration: 'Pier3AddOns;

With the scripting API, #currentVersion is loaded. Instead Metacello
records the version (project spec) of the project that was actually loaded
and is much more accurate ...

You do have to use the the `Metacello new` style load expressions to cause
projects to be registered ...


On Thu, Oct 23, 2014 at 9:46 AM, dtrussardi at tiscali.it <
dtrussardi at tiscali.it> wrote:

> Ciao,
> First i load:
>  Gofer new
>      url: 'http://www.squeaksource.com/MetacelloRepository';
>      package: 'ConfigurationOfPier3AddOns';
>      load.
> After i do :
>  ( ConfigurationOfPier3AddOns project version: '3.0.4') load.
> now i don't understund because after :
> ConfigurationOfPier3AddOns project currentVersion.
> answer  <>3.1.1 [ConfigurationOfPier3AddOns]
> and not 3.0.4
> Thanks,
> Dario
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20141023/8af8bfc0/attachment.htm

More information about the seaside mailing list