Tell the user to rename and make executable the binary they download in the README
Simply "moving the downloaded binary" to your PATH doesn't work.
Provide example commands:
wget <binary_release_url>
mv <downloaded_binary> <somewhere_in_your_path>
chmod u+x <new_path_to_binary>
This would save new folks a lot of trouble.
/assign
The recommendation by life5ign seems still not to have been implemented after nearly a year. We're talking about adding a few lines of text to a file that would have potentially saved me tens of hours of head-banging troubleshooting.
I was getting an error declaring "the executable not being in my $PATH", when actually the file was there, and it was in my $PATH. It just wasn't executable due to a permissions misconfiguration. 644 vs 744 = huge waste of time!
Please update your README for the love of God... and aspiring computer geeks everywhere. Well, I know a lot more about $PATHs now. So, thanks. I guess?
Here is the update for the README:
4 - Change the permissions to make the file executable.
$ chmod u+x /usr/local/bin/docker-credential-osxkeychain