>From f30716273f949d5883b7ced5c65ed5d48697479e Mon Sep 17 00:00:00 2001 From: Emma Turner Date: Mon, 19 Sep 2022 06:59:25 +0100 Subject: [PATCH] doc: contrib: recommend guix git authenticate * doc/contributing.texi (Building from git): recommend use of guix git authenticate on every git pull --- doc/contributing.texi | 27 +++++---------------------- 1 file changed, 5 insertions(+), 22 deletions(-) diff --git a/doc/contributing.texi b/doc/contributing.texi index 17a54f94cc..4fbef71fe7 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -152,29 +152,12 @@ If anything fails, take a look at installation instructions (@pxref{Installation}) or send a message to the @email{guix-devel@@gnu.org, mailing list}. -From there on, you can authenticate all the commits included in your -checkout by running: - -@example -make authenticate -@end example - -The first run takes a couple of minutes, but subsequent runs are faster. - -Or, when your configuration for your local Git repository doesn't match -the default one, you can provide the reference for the @code{keyring} -branch through the variable @code{GUIX_GIT_KEYRING}. The following -example assumes that you have a Git remote called @samp{myremote} -pointing to the official repository: - -@example -make authenticate GUIX_GIT_KEYRING=myremote/keyring -@end example - @quotation Note -You are advised to run @command{make authenticate} after every -@command{git pull} invocation. This ensures you keep receiving valid -changes to the repository. +As with the initial clone, you are advised to run @command{guix git authenticate} +after every @command{git pull} invocation. This ensures you keep receiving valid +changes to the repository (@pxref{Invoking guix git authenticate}). + +You will not be able to do this unless you already have Guix installed. @end quotation After updating the repository, @command{make} might fail with an error base-commit: f7565101e49102da6f87ad92e4644ae7996515ab -- 2.36.1