Fix unreplaced CSP policy value due to sed command in package.sh #404
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
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.
In the pre-built macOS release, as well as when built from source, the console shows an "invalid CSP value: {{cspValue}}" error. I saw that the
package.shbuild script tries to use an incompatible GNU version ofsed's in-place replacement option.To make it interoperable for both BSD and GNU sed versions, I changed it to make a .tmp backup of the original file and then delete it right after.
Which defeats the purpose of the "in-place" option flag, but at least it works.