[squeak-dev] Updating Squeak 4.5 to Squeak 4.6
asqueaker at gmail.com
Sat Jun 6 16:42:50 UTC 2015
Hmmm.... It's a good question. I, personally, have never wanted to
do that (upgrade 4.n ---> 4.n+1), because a new release image is the
best time to get a new clean image for my own applications to make
sure I can actually build inside the new image.
The only disadvantage I can see to your proposal is the duplicating
about 1000(?) mcz's to take up more space on disk.. unless making
soft links (hard links?) would solve that..?
On Sat, Jun 6, 2015 at 3:21 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
> Hi, there.
> If there are only the latest packages in the Squeak 4.6 repository, there
> may be many important mcm-checkpoints (together with
> postLoad-migration-scripts) are missing. Updating a busy 4.5 image to 4.6
> might fail easily.
> Don't we want to support that?
> View this message in context: http://forum.world.st/Updating-Squeak-4-5-to-Squeak-4-6-tp4830777.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
More information about the Squeak-dev