Permissions issue with rakudo install - suggest tweak to README

[librasteve]

hi - I am installing rakudo-moar-2021.10-01-macos-arm64-clang.tar.gz on a 100% factory restore Apple macOS Monterey on M1 (Terminal.app 'run using rosetta' off, but rosetta 2 installed) and had to go 'chmod +x set-env.sh' ... suggest edit this step into the README.md ...?

[librasteve]

oh - and there's a real error:

% eval "$(/Users/stephenroe/rakudo/rakudo-moar-2021.10-01-macos-arm64-clang/scripts/set-env.sh)"
/Users/stephenroe/rakudo/rakudo-moar-2021.10-01-macos-arm64-clang/scripts/set-env.sh: line 42: /bin/grep: No such file or directory
/Users/stephenroe/rakudo/rakudo-moar-2021.10-01-macos-arm64-clang/scripts/set-env.sh: line 42: /bin/grep: No such file or directory

fix is to edit
/bin/grep to /usr/bin/grep

[grondilu]

fix is to edit /bin/grep to /usr/bin/grep

Or just grep. I really don't see why an absolute path would be required here.

[lembark]

> > fix is to edit /bin/grep to /usr/bin/grep Or just `grep`. I really don't see why an absolute path would be required here.

Suggest checking "which grep" returning a value and croaking up front if it doesn't. Explicit sanity check up front allows for a saner error message "Unable to find 'grep' in path ..." vs. just failing mid-stream with a command not found error.

…

-- Steven Lembark Workhorse Computing ***@***.*** +1 888 359 3508