Basic functionality (and initial repro
crate)
#5
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.
Adds extremely basic functionality for invoking
cargo build --locked
ascargo repro build
.Though this may seem fairly pointless in and of itself, the goal of a followup commit would be to collect environmental information during this step (OS/release, rustc/cargo version, CWD, environment variables, git commit, C/C++ compiler versions if applicable) and use that during
the verification process to detect and highlight mismatches.
This commit attempts to split the CLI app (i.e.
cargo-repro
) from a library-level crate containing the core functionality (alacargo-audit
and therustsec
crate), in case there is interest in driving these sorts of builds from external tooling.