From f7b64f863f5d88fe45b9ce301ce799f4f8019fea Mon Sep 17 00:00:00 2001 From: Tobias Kortkamp Date: Thu, 28 Mar 2019 23:51:12 +0000 Subject: [PATCH] Porter's Handbook: Document CARGO_USE_GITLAB - Remove mention of CARGO_GH_CARGOTOML after ports r496795 - Update CARGO_USE_GITHUB description. It does not patch Cargo.lock. That is done automatically during the configure phase by cargo itself and is not worth mentioning here. Approved by: mat Differential Revision: https://reviews.freebsd.org/D19697 --- .../porters-handbook/special/chapter.xml | 20 +++++++++---------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml b/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml index b3d459cc45..0865c02804 100644 --- a/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml +++ b/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml @@ -997,21 +997,19 @@ CMAKE_OFF= VAR3 no Enable fetching of crates locked to specific Git commits on GitHub via GH_TUPLE. - This will try to patch both - Cargo.lock and - Cargo.toml to point to the + This will try to patch all + Cargo.toml under + WRKDIR to point to the offline sources instead of fetching them from a - Git repository during the build. Use with caution - as transitive Git dependencies are not resolved and - patched correctly. + Git repository during the build. - CARGO_GH_CARGOTOML - ${CARGO_CARGOTOML} - List of Cargo.toml that - will be patched when using - CARGO_USE_GITHUB. + CARGO_USE_GITLAB + no + Same as CARGO_USE_GITHUB + but for GitLab instances and + GL_TUPLE.