Ah, yes that was to be expected. There was a LOT of discussion among the
developers about the "proper" location for ooRexx to be installed on
*nix-like systems. We believe we now have it "right" but it is different
than it was for 4.2.0 so the hash-bang line was impacted. Sorry for the
extra work that caused you. I'll make sure the documentation covers that
change and its impact on existing shell scripts. As you've discovered,
there is a way to make the hash-bang line independent of the installed
location so it will work regardless of where ooRexx resides.
On 8/2/2020 9:29 AM, Cruz, Jaime wrote:
> On 8/1/20 10:21 AM, Gil Barmwater wrote:
>> If you don't mind sharing, I'n curious as to what you needed to change
>> in the first line that was keeping 5.0.0 from working?
>> Gil B.
> I don't think I have a copy of a script with the old comment line. The
> new comment line is:
> #!/usr/bin/env rexx
> The old one pointed to the directory where the REXX interpreter lived,
> but it seems that 5.0 gets installed into a different directory. The
> comment above works with both 4.2 and 5.0