[Glass] Which Grease to use with Seaside 3.1 in GemStone 3.2.9 and gsDevKit/tODE

[Dale Henrichs via Glass]

This is actually a "good" warning and proceeding is the correct action.

To get into specifics the conflict is occuring because the repository 
specified by Seaside 
(http://smalltalkhub.com/mc/SEaside/MetacelloConfigurations/main) is 
different that the locked repository 
(github://GsDevKit/Grease:master/repository) ... by honoring the lock 
(proceeding with Warning) the locked repository will continue to be used.

The GsDevKit/Grease repository is the master repository for 
GLASS/GsDevKit and should always be used, unless you clone it locally or 
fork your own ... in which case you will want to lock your own repo:)

Dale

On 10/14/2015 09:08 AM, Mariano Martinez Peck via Glass wrote:
> Hi guys,
>
> When I try to load Seaside3.1 in GemStone 3.2.9 I get a conflict 
> because 'Grease' is locked in GemStone. See attached screenshot. I 
> know how to fix it, but I don't know WHICH one of the 2 should be the 
> correct one. On the one hand, if 'Grease' was locked out of the box by 
> gsDevKit/tODE then I suspect that's the correct one. However, Seaside 
> was bringing another version (#release1.1).
>
> So my question is ... the locked version of Grease, should work 
> correctly with Seaside 3.1 in GemStone 3.2.9? I guess it should since 
> these instructions: https://github.com/GsDevKit/Seaside31
> keep a #honor on the lock.
>
> Thanks,
>
>
> -- 
> Mariano
> http://marianopeck.wordpress.com
>
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20151014/748180d1/attachment.html>