From 38d04053a46e06af1dd6818b9025dbf257665e8f Mon Sep 17 00:00:00 2001 From: Josiah Parry Date: Sun, 24 Sep 2023 07:45:07 -0400 Subject: [PATCH] Update vignettes/articles/cran-compliance.Rmd Co-authored-by: Ilia Kosenkov --- vignettes/articles/cran-compliance.Rmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vignettes/articles/cran-compliance.Rmd b/vignettes/articles/cran-compliance.Rmd index 3b6ea2be..98952a4f 100644 --- a/vignettes/articles/cran-compliance.Rmd +++ b/vignettes/articles/cran-compliance.Rmd @@ -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.