When I look at the latest version of Seaside-Tests-Core at
squeaksource.com, and when I look at the repo in-image in a Metacello
browser, the latest version is:
Seaside-Tests-Core-lr.219
However, version 305 of ConfigurationOfSeaside30 lists the version as:
Seaside-Tests-Core-as.220
I cann
More data from my build cache:
~/pub/builder/cache$ ls -l */Seaside-Core-as*
... 275758 Feb 7 07:32 Seaside 3.0/Seaside-Core-as.695.mcz
... 281915 Mar 10 07:32 Seaside 3.0/Seaside-Core-as.712.mcz
... 275758 Feb 7 08:32 WIP Seaside 3.0/Seaside-Core-as.695.mcz
... 281914 Mar 10 08:32 WIP Seaside
maybe it is at the seaside.gemstone.com/ss repo?
Am 2011-04-30 um 04:05 schrieb Yanni Chiu:
> More data from my build cache:
>
> ~/pub/builder/cache$ ls -l */Seaside-Core-as*
> ... 275758 Feb 7 07:32 Seaside 3.0/Seaside-Core-as.695.mcz
> ... 281915 Mar 10 07:32 Seaside 3.0/Seaside-Core-as.712.mc
What is the status of the projects hosted there?
Do they got synched from squeaksource?
Stefs
> maybe it is at the seaside.gemstone.com/ss repo?
> Am 2011-04-30 um 04:05 schrieb Yanni Chiu:
>
>> More data from my build cache:
>>
>> ~/pub/builder/cache$ ls -l */Seaside-Core-as*
>> ... 275758 Feb
Yanni,
We have had a bit of a dance lately with packages in the Seaside30 repo and the
configuration.
I don't know the actual details, but at various points in time over the last
month those "mystery packages" have appeared, disappeared, reappeared, then
disappeared again and I was lucky enoug
