[Seaside] upgrading methods
philippe.marschall at gmail.com
Fri Feb 23 19:12:10 UTC 2007
2007/2/23, Brad Fuller <brad at sonaural.com>:
> Philippe Marschall wrote:
> > 2007/2/23, Brad Fuller <brad at sonaural.com>:
> >> Philippe Marschall wrote:
> >> > FileLibrary is part of Seaside since October last year and since then
> >> > has been developed inside Seaside. Merging it is not a clever idea.
> >> Clever or not, there are several comments on this ml that suggested
> >> merging was preferable to loading. Don't know who said it. In fact, I
> >> 'loaded' my first upgrade test of Seaside/Magritte/Pier. It was
> >> disastrous. At least now I have the latest Seaside running ;-)
> > I feel there is some confusion about loading versus merging.
> > Loading replaces the code in you image with the code of the version
> > you load. This is similar to checking out a specific CVS/SVN revision.
> > Merging tries to figure out what changed between the code in the image
> > and the code of a version and only load those changes. Although this
> > sounds like a good idea, figuring out takes much more time than just
> > loading everything. This is more like a CVS/SVN update.
> yep, I got that. Thanks.
> > to sum up:
> > Loading is the right thing unless you have a branch or local changes.
> > You neither need to load nor merge file library.
> Why? It's a separate package. Is it now included in another package?
It is included in seaside, last October the classes were moved into
Seaside. Since then the development of the stand-alone package has
stopped and only the classes in the Seaside package have been
improved. Pier and Seaside will no longer work with the old,
stand-alone version of FileLibrary.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside