Skip to content

Commit

Permalink
Update vignettes/articles/cran-compliance.Rmd
Browse files Browse the repository at this point in the history
Co-authored-by: Ilia Kosenkov <[email protected]>
  • Loading branch information
JosiahParry and Ilia-Kosenkov authored Sep 24, 2023
1 parent 2ac41eb commit 38d0405
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion vignettes/articles/cran-compliance.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Additionally, to minimize security risks and ensure package stability, CRAN requ

Vendoring dependencies is the act of including the dependency itself into a packages source code. In the case of Rust, dependencies are fetched only at compile time. To enable compilation in an offline environment, dependencies must be vendored which is accomplished using the `cargo vendor` command.

`cargo vendor` creates a local directory, called `vendor/` by default, which contains the source code for each of the recursive dependencies of the crate that is being built. For CRAN compatibility, the `vendor/` directory must be compressed using tar xz compression and included in the source of the package.
`cargo vendor` creates a local directory with the default name `vendor`, which contains the source code for each of the recursive dependencies of the crate that is being built. For CRAN compatibility, the `vendor` directory must be compressed using tar xz compression and included in the source of the package.

During build time, the dependencies are uncompressed, compiled in the offline build, and discarded. This process is controlled by the `Makevars` and `Makevars.win` files.

Expand Down

0 comments on commit 38d0405

Please sign in to comment.