Use '/usr/bin/env bash' instead of '/bin/bash' for Linux scripts. - #894
Open
swagtop wants to merge 1 commit into
Open
Use '/usr/bin/env bash' instead of '/bin/bash' for Linux scripts.#894swagtop wants to merge 1 commit into
swagtop wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(Accidentally nuked old PR while rebasing for latest changes)
If
/usr/bin/env bashis used in the shebangs of the Linux scripts, thebashthat runs the script will be found in $PATH. This results in the scripts working on any systems that havebashavailable to the user, regardless of where it is located.In many systems
/bin/bashdoes not exist, as it is installed elsewhere. Using/usr/bin/env bashis a common way to avoid any portability issues between different Linux distributions.