Use frozen flag for cargo build
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | cargo.bbclass: Use --frozen flag for cargo operationsmeta/ | +6 | 0 replies | |
| 2/3 | cargo_common.bbclass: Handle Cargo.lock modifications for git dependenciesmeta/ | +40 | 2 replies | |
| 3/3 | cargo.bbclass: Offer a way to use --offline instead of --frozenmeta/ meta/ meta/ | +8 | 10 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Use frozen flag for cargo build
From: Frederic Martinsons <[email protected]>
This patch series force the usage of --frozen instead of --offline during cargo build. This has the advantage to be sure that Cargo.lock file will not be modified. Moreover, raise a clear error when Cargo.lock is not present.
For this to work, we must modify ourself the Cargo.lock before building in case there are git repo that have been patched.
The last commit is to handle the specific case of rust-hello-world recipe. If this recipe is no more necessary, we can drop this last patch.
The following changes since commit 9b5b850d6a6982bb8ff14dcfbb6769b293638293:
libarchive: ignore CVE-2023-30571 (2023-07-30 12:00:13 +0100)
are available in the Git repository at:
https://gitlab.com/fmartinsons/openembedded-core 15104-check-cargo-lock
Frederic Martinsons (3):
cargo.bbclass: Use --frozen flag for cargo operations cargo_common.bbclass: Handle Cargo.lock modifications for git
dependencies
cargo.bbclass: Offer a way to use --offline instead of --frozen
meta/classes-recipe/cargo.bbclass | 9 +++- meta/classes-recipe/cargo_common.bbclass | 43 +++++++++++++++++++ .../rust-example/rust-hello-world_git.bb | 2 + 3 files changed, 53 insertions(+), 1 deletion(-)
Signature · 1 line
2.34.1