Fix sudo check for non-existent install directories#18
Merged
Conversation
When the install directory doesn't exist yet, walk up to the first existing ancestor to check writability, rather than checking the non-existent directory itself (which always returns false and incorrectly triggers sudo).
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.
Summary
[ -w "$INSTALL_DIR" ]always returns false, causing the script to incorrectly requiresudoeven for user-owned paths like~/.local/binsudois not available (e.g. GitHub Actions runners)Test plan
~/.local/binon a system where the directory doesn't exist yet completes withoutsudo/usr/local/bin) still correctly invokessudosetup-lucaaction no longer fails withsudo: command not found