aboutsummaryrefslogtreecommitdiff
path: root/doc/documentation/gnunet-c-tutorial.texi
diff options
context:
space:
mode:
authorng0 <ng0@infotropique.org>2017-10-26 12:28:28 +0000
committerng0 <ng0@infotropique.org>2017-10-26 12:28:28 +0000
commite2f0870adf4baad5dfefaefd92c122ee9e1e0e5a (patch)
tree9374b281f7f450e9bd6c73ace85bb6d627fdd9d9 /doc/documentation/gnunet-c-tutorial.texi
parent17e755c71521be9a84f0f3b46d1de6962298f733 (diff)
downloadgnunet-e2f0870adf4baad5dfefaefd92c122ee9e1e0e5a.tar.gz
gnunet-e2f0870adf4baad5dfefaefd92c122ee9e1e0e5a.zip
documentation
Diffstat (limited to 'doc/documentation/gnunet-c-tutorial.texi')
-rw-r--r--doc/documentation/gnunet-c-tutorial.texi51
1 files changed, 35 insertions, 16 deletions
diff --git a/doc/documentation/gnunet-c-tutorial.texi b/doc/documentation/gnunet-c-tutorial.texi
index aca40d2ef..b62db7855 100644
--- a/doc/documentation/gnunet-c-tutorial.texi
+++ b/doc/documentation/gnunet-c-tutorial.texi
@@ -160,6 +160,16 @@ $ gpg --keyserver keys.gnupg.net --recv-keys 48426C7E
160@noindent 160@noindent
161and rerun the @code{gpg --verify-files} command. 161and rerun the @code{gpg --verify-files} command.
162 162
163@b{Note:}@
164@b{The pub key to sign the 0.10.1 release has been
165revoked}. You will get an error message stating that
166@i{there is no known public key or that it has been revoked}.
167The next release of GNUnet will have a valid signature
168again. We are sorry for the inconvenience this causes.
169Another possible source you could use is our
170"gnunet" git repository which has mandatory signed commits
171by every developer.
172
163Now you can extract the tarball and rename the resulting 173Now you can extract the tarball and rename the resulting
164directory to @i{gnunet} which we will be using in the 174directory to @i{gnunet} which we will be using in the
165remainder of this document. 175remainder of this document.
@@ -178,14 +188,19 @@ from @uref{https://gnunet.org/git/, git}.
178@node Installing Build Tool Chain and Dependencies 188@node Installing Build Tool Chain and Dependencies
179@section Installing Build Tool Chain and Dependencies 189@section Installing Build Tool Chain and Dependencies
180 190
181To successfully compile GNUnet you need the tools to build GNUnet and 191To successfully compile GNUnet, you need the tools to build GNUnet and
182the required dependencies. Please have a look at 192the required dependencies. Please take a look at the
183@uref{https://gnunet.org/dependencies} for a list of required dependencies 193GNUnet Reference Documentation
184and @uref{https://gnunet.org/generic_installation} for specific 194(@pxref{Dependencies, The GNUnet Reference Documentation,, gnunet, The GNUnet Reference Documentation})
185instructions for your operating system. Please check the notes at 195for a list of required dependencies
186the end of the configure process about required dependencies. 196and
187 197(@pxref{Generic installation instructions, The GNUnet Reference Documentation,, gnunet, The GNUnet Reference Documentation})
188For GNUnet bootstrapping support and the http(s) plugin you should 198read its Installation chapter for specific instructions for
199your operating system.
200Please check the notes at the end of the configure process about
201required dependencies.
202
203For GNUnet bootstrapping support and the HTTP(S) plugin you should
189install @uref{https://gnunet.org/gnurl, libgnurl}. 204install @uref{https://gnunet.org/gnurl, libgnurl}.
190For the filesharing service you should install at least one of the 205For the filesharing service you should install at least one of the
191datastore backends. MySQL, SQlite and PostgreSQL are supported. 206datastore backends. MySQL, SQlite and PostgreSQL are supported.
@@ -194,8 +209,8 @@ datastore backends. MySQL, SQlite and PostgreSQL are supported.
194@section Obtaining the latest version from Git 209@section Obtaining the latest version from Git
195 210
196The latest development version can obtained from our Git repository. 211The latest development version can obtained from our Git repository.
197To obtain the code you need Git installed and checkout the repository 212To obtain the code you need to have @code{Git} installed, which is
198using: 213required for obtaining the repository via:
199 214
200@example 215@example
201$ git clone https://gnunet.org/git/gnunet 216$ git clone https://gnunet.org/git/gnunet
@@ -203,21 +218,25 @@ $ git clone https://gnunet.org/git/gnunet
203 218
204@noindent 219@noindent
205After cloning the repository you have to execute the @file{bootstrap} 220After cloning the repository you have to execute the @file{bootstrap}
206script in the directory: 221script in the new directory:
207 222
208@example 223@example
209$ cd gnunet ; ./bootstrap 224$ cd gnunet
225$ ./bootstrap
210@end example 226@end example
211 227
212@noindent 228@noindent
213The remainder of this tutorial assumes that you have the Git branch 229The remainder of this tutorial will assume that you have the
214``master'' checked out. 230Git branch ``master'' checked out.
215 231
216@node Compiling and Installing GNUnet 232@node Compiling and Installing GNUnet
217@section Compiling and Installing GNUnet 233@section Compiling and Installing GNUnet
218 234
219First, you need to install at least libgnupgerror 1.27 and 235Note: This section is a duplication of the more in depth
220libgcrypt 1.7.6. 236@pxref{GNUnet Installation Handbook, The GNUnet Reference Documentation,, gnunet, The GNUnet Reference Documentation}.
237
238First, you need to install libgnupgerror @geq{} 1.27 and
239libgcrypt @geq{} 1.7.6:
221 240
222@example 241@example
223$ export GNUPGFTP="https://www.gnupg.org/ftp/gcrypt" 242$ export GNUPGFTP="https://www.gnupg.org/ftp/gcrypt"