Be forgiving when --prefix passed with trailing '/'
#513
Conversation
This file contains 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
Passing --prefix=/home/foo/bar/ would result in "//" being generated in the replacements, causing potential troubles. This adds a little bit of robustness around that for the configure script, chopping it off if present, and being smarter than blindly `string-append`ing parts that are to be joined.
fare
approved these changes
May 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Passing --prefix=/home/foo/bar/ would result in "//" being generated
in the replacements, causing potential troubles. This adds a little
bit of robustness around that for the configure script, chopping it
off if present, and being smarter than blindly
string-appendingparts that are to be joined.