I agree with what you’re saying. I just did the obvious. I moved the squeak script (as in your post) manually to be /usr/bin/squeak. 
I moved the /squeak/5.0-2018…snip to /usr/bin/lib/squeak/5.0-2018…snip. Works now. (Probably a bit wrong, but I’ll take it.) 
I figured Ian’s script was doing something simpler than I supposed. Now $squeak [ -help | -version ] works as expected. 
I kept bouncing off a error: "Could not determine platform's libc path for VM.” I googled it, found Pharo’s had a question about their PharoLauncher on Ubuntu about a year ago. [1] I just kept reading the error until it and I agreed on where I was putting things. 
As a closer, I’ll say that the squeak script only exists in the All-In-One. In the Linux specific download you get squeak.sh, which I don’t suppose is a candidate to put in /usr/bin/. You’d think it might be the other way around. 
I’ll try some shebang scripts tomorrow. 

Thanks, 
Chris 


[1] http://forum.world.st/Problem-with-PharoLauncher-on-Ubuntu-18-04-64-bit-td5078117.html


> On May 20, 2019, at 7:38 PM, tim Rowledge <tim at rowledge.org> wrote:
> 
> 
> 
>> On 2019-05-20, at 4:32 PM, Chris Cunnington <brasspen at gmail.com> wrote:
>> 
>> Thanks, I that jarred my mind into the solution. I’ll try the script tomorrow. 
> 
> I really don't know what the best unix answer is. On the Pi we seem to have been ok with this /usr/bin/squeak - 
> <squeak>
> and the vm(s) go in /usr/lib/squeak/{version numbery thing}/squeak. The script finds the latest one (except I see now a dependence on it being a 5.0-something version so that could do with improving) and faffs around with a load of stuff I won't even pretend to know about.
> 
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Oxymorons: Tight slacks
> 
> 
>