feat: use new sandbox fields from pacmanconf for git feature #58
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
pfeifferj
force-pushed
the
feat/use-new-sandbox-fields-from-pacmanconf
branch
from
9039e5c to
8de9ec1
Compare
Update alpm-utils to use the new disable_sandbox_filesystem and disable_sandbox_syscalls fields from pacmanconf when the git feature is enabled, instead of using the legacy disable_sandbox field for both. Signed-off-by: Josephine Pfeiffer <hi@josie.lol>
pfeifferj
force-pushed
the
feat/use-new-sandbox-fields-from-pacmanconf
branch
from
8de9ec1 to
03e0538
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Update alpm-utils to use the new disable_sandbox_filesystem and disable_sandbox_syscalls fields from pacmanconf when the git feature is enabled, instead of using the legacy disable_sandbox field for both.