Morphic issue with Seaside version on Lukas's build server and Metacello configurations

Hi
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Opps keyboard error:
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Nick,

You cannot load Metacello versions on top of the images I build, because Metacello typically depends on old code and the images I build use the HEAD of everything.

To get a working image either load Magritte3 on top of an empty image, or load the HEAD with one of the images I build.

Lukas

On Wednesday, March 21, 2012, Nick Ager <[hidden email]> wrote:
> Opps keyboard error:
> ----
>
> Hi
> If I download the latest Seaside build from Lukas's build server [1] and then try to load Magritte 3 on-top using:
> Gofer it
> squeaksource: 'MetacelloRepository';
>    package: 'ConfigurationOfMagritte3';
>    load.
> ConfigurationOfMagritte3 project stableVersion load: 'Seaside'.
> the result is that the Seaside control panel produces a walk-back. It seems that the version of Morphic loaded by Metacello is incompatible with the version used on the build server.
> The walk-back stems from OBLazyListMorph>>#display:atRow:on:
> It seems Metacello is loading a different version of OBLazyListMorph.
> My knowledge of Morphic and Metacello is limited so I'm afraid I'm stuck. Any thoughts?
> Nick

--
Lukas Renggli (mobile)
http://www.lukas-renggli.ch

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi Lukas,
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>> You cannot load Metacello versions on top of the images I build, because
>> Metacello typically depends on old code and the images I build use the HEAD
>> of everything.
>
> Does this mean that when make a new release [1] it should be based on a
> Pharo base 1.3/1.4 or from you build server? If we use builder server images
> as the basis then users will have a problem using Metacello base
> configurations... unless I've missed something.

It doesn't need to be a build from my build server.

I don't think that all of the past releases were.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside