diff options
| author | Leo Famulari <leo@famulari.name> | 2021-04-04 13:28:46 -0400 |
|---|---|---|
| committer | Leo Famulari <leo@famulari.name> | 2021-04-04 13:34:30 -0400 |
| commit | 5b97804e8714cfaeabf12b7c0e8530737907965f (patch) | |
| tree | 5d49dfc3b9431c693e50755dfe2cd81297833701 /doc | |
| parent | b5d7ea6f37186905931374a7cbbca23af6e8eec8 (diff) | |
doc: Remind developers to build Guix.
The previous instructions were correct, but we got too many bug reports
with a root cause of "did not build Guix yet".
Other parts of the manual already instruct `make && make check`, so this
makes the treatment of building Guix more consistent, too.
* doc/contributing.texi (Building from Git): Instruct the user to run
`make` when building Guix.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/contributing.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi index 1cf345a3de..9a09de93e6 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -126,10 +126,10 @@ Store}, for information about this), usually @file{/var}. Note that you will probably not run @command{make install} at the end (you don't have to) but it's still important to pass the right @code{localstatedir}. -Finally, you have to invoke @code{make check} to run tests -(@pxref{Running the Test Suite}). If anything -fails, take a look at installation instructions (@pxref{Installation}) -or send a message to the @email{guix-devel@@gnu.org, mailing list}. +Finally, you have to invoke @code{make && make check} to build Guix and +run the tests (@pxref{Running the Test Suite}). 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: |