Re: Squeak-dev Digest, Vol 282, Issue 23

> On Jun 15, 2026, at 8:28 PM, Ralph Boland <[email protected]> wrote:
> 
> I am in the habit of having multiple Squeak set ups on my (Linux) computer.
> And at any given time I can run any one of them.

Likewise- I typically have many different squeak systems in use and often many running simultaneously.


> Does your proposed setup allow for this?

The directory layout seems like something that shouldn’t really have much effect on this, as long as it isn’t causing over-writing of files in a bad way. [1] Using a shell script that can examine the header of the image file allows for selecting the correct VM to run; Dave L’s script does/did that a long time ago.
Adding an action to the new-image-wizard should also help reduce this problem for starting ‘clean’ images.

> Using an environment variable would help but seems clumsy.

Very probably.

[1] Actually this is something that we screw up rather badly in some important situations. Imagine starting up an image, doing some do-its or changes, and then accidentally or otherwise starting the same image file again; now two systems are writing to the same .changes file without any real restrictions. Worse yet, the completely wrong way file writing is done (seek to position, write stuff to current position) allows for chaos.


tim
--
tim Rowledge; [email protected]; http://www.rowledge.org/tim
Strange OpCodes: HAL: Murder Operator


Squeak-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]