Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server/scripts/build-wrapper.sh should not presume bash path #426

Conversation

TheCapsLock
Copy link
Contributor

No description provided.

@rom1v
Copy link
Collaborator

rom1v commented Feb 17, 2019

I think I prefer to refer explicitly to /bin/bash (in case some bash binary is elsewhere accessible from PATH).

Where is your bash in practice?

@TheCapsLock
Copy link
Contributor Author

In my case ; it happens scrcpy is run under NixOS. it is an operating system where binaries path are changed after each derivation (roughly upgrade).

I know other folks like BSD users which does not have bash on /bin/bash. It seems to me that using /usr/bin/env is the most interoperable way to go when writing bash scripts

@rom1v rom1v added the undecided label May 5, 2019
@rom1v
Copy link
Collaborator

rom1v commented Oct 31, 2019

Do someone have a strong opinion on this?

Personally, I prefer /bin/bash (more standard and less "risky").

rom1v pushed a commit that referenced this pull request Sep 15, 2020
PR #426 <#426>

Signed-off-by: Romain Vimont <rom@rom1v.com>
rom1v added a commit that referenced this pull request Sep 15, 2020
@rom1v
Copy link
Collaborator

rom1v commented Sep 15, 2020

Merged on dev as cf7bf31

@rom1v rom1v closed this Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants