[squeak-dev] managing the transition to 64-bit

Chris Muller ma.chris.m at gmail.com
Mon Dec 12 17:52:39 UTC 2016

I'm ready to make a push to migrate all my stuff to 64-bit, so this
means I need the ability to run either a 32-bit VM or a 64-bit VM, at
least for now.  Unfortunately, it appears each uses the same the VM
file directory structure, and so whichever one is installed last
stomps out the other.

Eliot, you have unique names for VM versions, have you considered
inserting something to uniquefy the names to support co-existence of
32 and 64-bit of the same VM version?  Or, does anyone have any best
practices to allow the co-existence of 32-bit with 64-bit VM?

I'm not talking about the problem with the names of the executables
(scripts) all being "squeak".  I've already been renaming the shell
scripts from "squeak" to "cog" or "spur".  Now the problem between 32
and 64-bit is the "lib" directory they refer to -- they share the
exact same name.

I still have a lot of 32-bit images around.  Does anyone have any
pointers on how best to manage both a 32-bit and 64-bit?

More information about the Squeak-dev mailing list