RPM rule integrity and mnemonics #62
Merged
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
Mnemonics are required to modify the execution info of a rule using: build --modify_execution_info=Rpm2Tar=+no-remote
|
Cool! |
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.
Two small changes:
Add "integrity" as alternative for "sha256" in rpm rule
This is an alternative format for specifying the expected hash. It specifies the expected checksum in Subresource Integrity format of the file downloaded.
Add mnemonics to rpm2tar and tar2files
When using remote cache in Bazel, some IO intensive actions are slower when using the remote cache (vs always redoing the action locally). This behavior can be controlled using the flag
--modify_execution_info.See also: https://blog.aspect.dev/bazelrc-flags