seccomp tools: add package #4476
Open
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
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.
Closes #4475
It used rake to compile binary module so I had to append
bundle exec rakerelated things in.installfile. I did not executerubocodeorspec, which performs static inspection and tes B0D4 t the code.Patches are used to maintain the module finding path, allowing users feel free to call this tool from anywhere, without being forced to
$realpath(...)I set a environment variable because I don't want to get into the hell of creating many ruby dependency packages I don't really know about, instead I allowed ruby to use the one installed locally inside the package by
bundle installcommand.I've also removed
specdirectory because what I saw in it are just tests.