From: Christian Grothoff Date: Tue, 19 Feb 2019 14:43:27 +0000 (+0100) Subject: remove obsolete comments X-Git-Tag: v0.11.0~63^2~32^2~9^2 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=a47969b03be93336a15c2500e8ca510597b53c21;p=oweals%2Fgnunet.git remove obsolete comments --- diff --git a/README b/README index a6ca4cabd..64d4fd422 100644 --- a/README +++ b/README @@ -166,22 +166,12 @@ Building GNUnet from source ~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT: You can read further notes about compilation from source in -the 'doc/FILENAME' document, which includes notes about specific +the handbook under doc/handbook/, which includes notes about specific requirements for operating systems aswell. If you are a package mantainer for an Operating System we invite you to add your notes if you feel it is necessary and can not be covered in your Operating System's documentation. -If you are building GNUnet from source you are either interested -in furthering its development (we have further notes for developer -builds in our 'GNUnet Developer Handbook') or you don't trust other -people's binaries or your Operating System doesn't provide any -binary package (at the moment). - -If you're on Gentoo you can build GNUnet using the recipes provided -in the 'youbroketheinternet' overlay. Other Operating Systems may -unintentionally require you to build GNUnet from source. - Two prominent examples which currently lack cross-compilation support in GNUnet (and native binaries) are MS Windows and Apple macOS. For macOS we recommend you to do the build process via Homebrew and a @@ -317,7 +307,7 @@ Usage ===== For detailed usage notes, instructions and examples, refer to the -included 'GNUnet User Handbook'. +included 'GNUnet Handbook'. First, you must obtain an initial list of GNUnet hosts. Knowing a single peer is sufficient since after that GNUnet propagates