Hi Eliot,

On Fri, Feb 07, 2020 at 11:36:12AM -0800, Eliot Miranda wrote:
> On Fri, Feb 7, 2020 at 11:33 AM Eliot Miranda <eliot.miranda at gmail.com>
> wrote:
> 
> > Tobias,
> >
> > On Fri, Feb 7, 2020 at 11:21 AM Tobias Pape <Das.Linux at gmx.de> wrote:
> >
> >>
> >> > On 07.02.2020, at 20:07, David T. Lewis <lewis at mail.msen.com> wrote:
> >> >
> >> > Technically,
> >> > it would be hard to do this from a single compiled VM executable, but
> >> > fortunately that is not needed.
> >>
> >> It's possible, tho. RSqueak at one point happily read 64bit and 32bit
> >> images all the same???
> >>
> >
> > Of course it's possible.  But it makes no sense to me.  One only needs to
> > convert once so why complicate the Vm including an extremely rarely used
> > action that is slooow?  If we include this facility soon enough people will
> > complain that launching a 32-bit image takes ages.  It is *much better
> > engineering* to require people to convert once using a separate tool than
> > complicating the existing production VM with a facility that is hardly ever
> > used.
> >
> 
> And if *you* want the facility, why don't *you* write it and test it,
> instead of expecting me to add it as yet another task to my high list of
> completely unfunded things to do for the VM?
> 

Hi Eliot,

I think you are reading too much into Tobias' reply :-)

My "is there any interest" question was referring to the idea of
coming up with distict naming conventions for the various VM
installations.

To say it another way, if I have Cog installed on my Linux box, and
then I install 32-bit Spur, it overwrites the /usr/local/bin/squeak
file.  And if I then isntall 64-bit Spur, it overwrites the one for
32-bit Spur. They also conflict with the original /usr/local/bin/squeak.

This is easily fixable if there is an interest, hence my question.

Dave