DOC: use -p with mkdir ~/bin since might exist already

[yarikoptic]

No description provided.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
• In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

[yarikoptic]

I signed it!

[googlebot]

CLAs look good, thanks!

[r2d4]

This change LGTM, but shouldn't we be downloading to /usr/local/bin or something other than $HOME/bin, which isn't standard? We can remove the $PATH modifying too, which won't work for new shells @nkubala

[yarikoptic]

there is a snippet for /usr/local/bin installation already (via sudo, since user might not have permissions to mess with it as well).
I am curious -- what did you mean by $PATH modifying ... won't work for new shells?

[r2d4]

You need to add export PATH=$PATH:$HOME/bin to your bashrc or a similar startup script, otherwise when you open a new shell, the path variable won't include your changes.

[yarikoptic]

ah, I just misread your statement, and by "new shells" meant really new types of shells etc, not just new shell sessions. Thanks for the explanation.
yeah -- in my case PATH already includes ~/bin ;)

[nkubala]

Yeah this is just a second option if users don't want to use sudo to copy to /usr/local/bin or another shared directory.

[r2d4]

Oh sorry, didn't see that!