[Seaside-dev] Seaside 3.0 final and Pharo 1.0

[Lukas Renggli]

Seaside 3.0 final depends on changes only present in Pharo 1.1.

Of course it would be possible to support Pharo 1.0 with appropriate
Grease and Seaside support packages, however I doubt that this is
worth the trouble. Most development packages (RB, OB, ...) only work
on Pharo 1.1 too.

Lukas

On 5 October 2010 22:47, Dale Henrichs <dhenrich at vmware.com> wrote:
> I am building the configuration for the 3.0 final release and I'm getting a
> bunch of test failures in Pharo1.0:
>
>  1652 run, 1609 passes, 2 expected failures, 0 failures, 41 errors,
>    0 unexpected passes
>
> It looks like the errors are due to the removal of Collection>>#sorted,
> Collection>>#sorted: and WriteStream class>>crlf... from Grease-Pharo-Core
> ...
>
> So I'm just wondering if it is intentional to _not_ support Seaside3.0 on
> Pharo1.0.
>
> There are similar problems with earlier versions of Pharo 1.1
> (Pharo-1.1-11411dev10.07.1 for example), but presumably the errors could be
> fixed by updating to the latest ...
>
> It would be relatively straightforward to fix the problem at the cost of an
> extra package for Pharo 1.0 (and earlier development versions of Pharo1.1)
> if you are interested in making life easier for folks using Seaside3.0 on
> those versions of Pharo.
>
>
> Dale
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>



-- 
Lukas Renggli
www.lukas-renggli.ch