-
Notifications
You must be signed in to change notification settings - Fork 0
fix: configurable install dir for relacs #107
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
Open
tommartensen
wants to merge
16
commits into
main
Choose a base branch
from
tm/configurable-install-dir-relacs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+79
−3
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
374cd15
fix: configurable install dir for relacs
tommartensen d3116b8
fix defaulting to /Users/tmartens/.local/bnin
tommartensen 47996b0
resolve better
tommartensen a0272ac
update comment
tommartensen 1283a57
address security finding about interpolating bash variables
tommartensen 7d460d3
Update bash scripts according to new, memorized style guide
tommartensen 8bcc22b
Rename binary_dir parameter to relacs_install_dir
tommartensen 740cc31
document that $HOME will be expanded in custom paths
tommartensen 65d617b
make relacs binary name configurable
tommartensen 7635557
switch to relacs-install-path
tommartensen 9161184
add comment about command injection
tommartensen 353362c
don't expand HOME_SWEET_HOME
tommartensen 501eaac
use install-relacs script from default branch
tommartensen a0d2038
fix: add fi
tommartensen 2410ea9
Update release/install-relacs/action.yml
tommartensen b1580a7
add comment about $
tommartensen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm. Is it a real syntax
$HOME$/blahand${HOME}$/blah?I know it's annoying but we should try make it right.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
$SOMETHING\$in double quotes is interpreted to$SOMETHING$in the sed expression, where the last $ is the end-of-line character.$HOME$/blahwould not be matched (and not be expanded), it's not a valid path.Added a comment explaining the
\$intention.Details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I skipped
Detailsin your reply because they strongly smell AI.I get your idea is to prevent
$HOME_SWEET_HOMEby making sure that$HOMEor${HOME}is followed by a/slash or end of line. I doubt that the latter is valid case for$RELACS_INSTALL_PATH, but it's going to be the user's fault to set it to plain$HOME.What blows my mind is that the last
$in$SOMETHING$sed expression acts as the end-of-line match but the first$does not. This absence of sed expression-level escaping for the first$is quite confusing when just looking at this code.Did you evaluate
printf '%s' "$RELACS_INSTALL_PATH" | envsubst '$HOME'as the alternative to the approach withsedand why is it not good?