os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Porter's Handbook: Document CARGO_USE_GITLAB

Browse source 
- 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
This commit is contained in:
Tobias Kortkamp 2019-03-28 23:51:12 +00:00
parent d2f8d7bbc1
commit f7b64f863f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=52900
1 changed files with 9 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
en_US.ISO8859-1/books/porters-handbook/special/chapter.xml
View file

@ -997,21 +997,19 @@ CMAKE_OFF= VAR3</programlisting>
<entry><literal>no</literal></entry>
<entry>Enable fetching of crates locked to specific Git
commits on GitHub via <varname>GH_TUPLE</varname>.
This will try to patch both
<filename>Cargo.lock</filename> and
<filename>Cargo.toml</filename> to point to the
This will try to patch all
<filename>Cargo.toml</filename> under
<varname>WRKDIR</varname> 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.</entry>
Git repository during the build.</entry>
</row>
<row>
<entry><varname>CARGO_GH_CARGOTOML</varname></entry>
<entry><literal>${CARGO_CARGOTOML}</literal></entry>
<entry>List of <filename>Cargo.toml</filename> that
will be patched when using
<varname>CARGO_USE_GITHUB</varname>.</entry>
<entry><varname>CARGO_USE_GITLAB</varname></entry>
<entry><literal>no</literal></entry>
<entry>Same as <varname>CARGO_USE_GITHUB</varname>
but for GitLab instances and
<varname>GL_TUPLE</varname>.</entry>
</row>
</tbody>
</tgroup>