[Glass] Grease and Seaside31

[Johan Brichau]

Hi Dale,

I defined a tag '3.1.1-gs31' for Seaside 3.1.1 in ConfigurationOfSeaside3-JohanBrichau.145

	spec for: #'gs3.x' do: [
		spec baseline: 'Seaside3' with: [
				spec repository: 'github://glassdb/Seaside31:3.1.1-gs31/repository' ]. ].

So, I think that 3.1.1 is always loading that specific release, no?

Note that I tried explicitly writing the ConfigurationOfSeaside such that Grease for Gemstone was fetched from the github repository, but I encountered some troubles. I think we exchanged some mails about that either on this list or the metacello group, but I cannot put my hands on them for now. I will keep looking.

cheers
Johan


On 04 Jun 2014, at 20:38, Dale Henrichs <dale.henrichs at gemtalksystems.com> wrote:

> I am starting to get busy characterizing and fixing Seaside3.1.1 issue #21[1].
> 
> The issue involves UTF8 performance and a fair amount of the UTF8 support is located in the Grease project.
> 
>  Sooo, I am inclined to start using the Github-based Grease repository ... the packages are all synchronized with the packages on smalltalk hub (thanks Johan!).
> 
> The upshot will be that Seaside3.1.1 will still use ConfigurationOfGrease, but just as Johan has done for ConfigurationOfSeaside3, the configuration will directly reference the github repository.
> 
> BTW, Johan, I notice that the reference in ConfgurationOfSeaside# that you did not point to a specific SHA, which means that folks loading Seaside3.1.1.1 could get different versions. I think it should be frozen at 9c53917253e0512a8a3ffd569b6d20fea8c5179e... what do you think?
> 
> Dale
> 
> [1] https://github.com/glassdb/Seaside31/issues/21
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass