No redo during installation

[nncp.git] / doc / building.texi

diff --git a/doc/building.texi b/doc/building.texi
index 5aa7f10f5e7318e446584d2b71fe9f1e78cc96e2..af28f753a88888ce6559afe6271481b94a72246c 100644 (file)
--- a/doc/building.texi
+++ b/doc/building.texi
@@ -17,7 +17,7 @@ $ [fetch|wget] http://www.nncpgo.org/download/nncp-@value{VERSION}.tar.xz.asc
 $ gpg --verify nncp-@value{VERSION}.tar.xz.asc nncp-@value{VERSION}.tar.xz
 $ xz --decompress --stdout nncp-@value{VERSION}.tar.xz | tar xf -
 $ cd nncp-@value{VERSION}
-$ redo all
+$ bin/build
 @end example
 
 @pindex info
@@ -27,22 +27,6 @@ necessary installation). For example, documentation for
 @command{nncp-bundle} command can be get with
 @command{info doc/nncp.info -n nncp-bundle}.
 
-@pindex redo
-@pindex apenwarr/redo
-@pindex apenwarr/do
-@pindex redo-c
-@pindex baredo
-@pindex goredo
-It uses @url{http://cr.yp.to/redo.html, redo} build system for that
-examples. You can use one of its various implementations, or at least
-minimalistic POSIX shell @command{contrib/do} (just replace
-@command{redo} with @command{contrib/do} in the example above) included
-in tarball. Following ones are tested to work with:
-@url{http://www.goredo.cypherpunks.ru/, goredo} (NNCP's author creation),
-@url{https://redo.readthedocs.io/, apenwarr/redo} (@code{contrib/do} is
-from that project), @url{https://github.com/leahneukirchen/redo-c, redo-c},
-@url{https://github.com/gotroyb127/baredo, baredo}.
-
 @vindex PREFIX
 @vindex DESTDIR
 @vindex GO
@@ -72,25 +56,25 @@ respected during installation:
 @env{$INFODIR},
 @env{$DOCDIR}.
 
-There is @command{install} target for binaries and info-documentation
+There is @command{install} script for binaries and info-documentation
 installation:
 
 @example
-# PREFIX=/usr/local redo install
+# PREFIX=/usr/local ./install
 @end example
 
 @vindex nofsnotify
 @cindex kqueue
 @cindex epoll
 @vindex GO_CFLAGS
-NNCP depends on @code{github.com/fsnotify/fsnotify} library, that is
-solely relies on OS-specific mechanisms. There is possibility that you
-have either broken or unsupported ones. You can still build NNCP with
+NNCP depends on @code{github.com/fsnotify/fsnotify} library, that solely
+relies on OS-specific mechanisms. There is possibility that you have
+either broken or unsupported ones. You can still build NNCP with
 @code{-tags nofsnotify} build option, to skip @code{fsnotify} library
 usage at all:
 
 @example
-$ GO_CFLAGS="-tags nofsnotify" redo @dots{}
+$ GO_CFLAGS="-tags nofsnotify" bin/build
 @end example
 
 @vindex noyggdrasil