[GNUnet-SVN] [gnunet] branch master updated: doc: installation: section 'outdated instructions', comment the part about gnunet-update

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new 1b97e6794 doc: installation: section 'outdated instructions', comment 
the part about gnunet-update
1b97e6794 is described below

commit 1b97e6794813ff5ad390a10e972ea92002d85ee4
Author: ng0 <address@hidden>
AuthorDate: Tue Oct 24 12:50:41 2017 +0000

    doc: installation: section 'outdated instructions', comment the part about 
gnunet-update
---
 doc/documentation/chapters/installation.texi | 124 +++++++++++++--------------
 1 file changed, 62 insertions(+), 62 deletions(-)

diff --git a/doc/documentation/chapters/installation.texi 
b/doc/documentation/chapters/installation.texi
index 6d7b7f926..14175a6f7 100644
--- a/doc/documentation/chapters/installation.texi
+++ b/doc/documentation/chapters/installation.texi
@@ -1338,7 +1338,7 @@ updates or any kind of support.
 * Installing GNUnet 0.10.1 on Ubuntu 14.04::
 * Building GLPK for MinGW::
 * GUI build instructions for Ubuntu 12.04 using Subversion::
-* Installation with gnunet-update::
address@hidden * Installation with gnunet-update::
 * Instructions for Microsoft Windows Platforms (Old)::
 @end menu
 
@@ -1545,90 +1545,90 @@ Now you can checkout and compile the GNUnet GUI tools@
  $ make install
 @end example
 
address@hidden Installation with gnunet-update
address@hidden Installation with gnunet-update
address@hidden @node Installation with gnunet-update
address@hidden @subsection Installation with gnunet-update
 
-gnunet-update project is an effort to introduce updates to GNUnet
-installations. An interesting to-be-implemented-feature of gnunet-update
-is that these updates are propagated through GNUnet's peer-to-peer
-network. More information about gnunet-update can be found at
address@hidden FIXME: Use correct cgit URL
address@hidden://gnunet.org/git/gnunet-update.git/tree/plain/README}.
address@hidden gnunet-update project is an effort to introduce updates to GNUnet
address@hidden installations. An interesting to-be-implemented-feature of 
gnunet-update
address@hidden is that these updates are propagated through GNUnet's 
peer-to-peer
address@hidden network. More information about gnunet-update can be found at
address@hidden @c FIXME: Use correct cgit URL
address@hidden 
@uref{https://gnunet.org/git/gnunet-update.git/tree/plain/README}.
 
-While the project is still under development, we have implemented the
-following features which we believe may be helpful for users and we
-would like them to be tested:
address@hidden While the project is still under development, we have 
implemented the
address@hidden following features which we believe may be helpful for users and 
we
address@hidden would like them to be tested:
 
address@hidden @bullet
address@hidden @itemize @bullet
 
address@hidden
-Packaging GNUnet installation along with its run-time dependencies into
-update packages
address@hidden @item
address@hidden Packaging GNUnet installation along with its run-time 
dependencies into
address@hidden update packages
 
address@hidden
-Installing update packages into compatible hosts
address@hidden @item
address@hidden Installing update packages into compatible hosts
 
address@hidden
-Updating an existing installation (which had been installed by
-gnunet-update) to a newer one
address@hidden @item
address@hidden Updating an existing installation (which had been installed by
address@hidden gnunet-update) to a newer one
 
address@hidden itemize
address@hidden @end itemize
 
-The above said features of gnunet-update are currently available for
-testing on GNU/Linux systems.
address@hidden The above said features of gnunet-update are currently available 
for
address@hidden testing on GNU/Linux systems.
 
-The following is a guide to help you get started with gnunet-update.
-It shows you how to install the testing binary packages of GNUnet
-0.9.1 we have at @uref{https://gnunet.org/install/}.
address@hidden The following is a guide to help you get started with 
gnunet-update.
address@hidden It shows you how to install the testing binary packages of GNUnet
address@hidden 0.9.1 we have at @uref{https://gnunet.org/install/}.
 
-gnunet-update needs the following dependencies:
address@hidden gnunet-update needs the following dependencies:
 
address@hidden @bullet
address@hidden
-python @geq{} 2.6
address@hidden @itemize @bullet
address@hidden @item
address@hidden python @geq{} 2.6
 
address@hidden
-gnupg
address@hidden @item
address@hidden gnupg
 
address@hidden
-python-gpgme
address@hidden itemize
address@hidden @item
address@hidden python-gpgme
address@hidden @end itemize
 
 
-Checkout gnunet-update:
address@hidden Checkout gnunet-update:
 
address@hidden FIXME: git!
address@hidden
-$ svn checkout -r24905 https://gnunet.org/svn/gnunet-update@
address@hidden example
address@hidden @c FIXME: git!
address@hidden @example
address@hidden $ svn checkout -r24905 https://gnunet.org/svn/gnunet-update@
address@hidden @end example
 
-For security reasons, all packages released for gnunet-update from us are
-signed with the key at @uref{https://gnunet.org/install/key.txt}.
-You would need to import this key into your gpg key ring.
-gnunet-update uses this key to verify the integrity of the packages it
-installs:
address@hidden For security reasons, all packages released for gnunet-update 
from us are
address@hidden signed with the key at @uref{https://gnunet.org/install/key.txt}.
address@hidden You would need to import this key into your gpg key ring.
address@hidden gnunet-update uses this key to verify the integrity of the 
packages it
address@hidden installs:
 
address@hidden
-$ gpg --recv-keys 7C613D78@
address@hidden example
address@hidden @example
address@hidden $ gpg --recv-keys 7C613D78@
address@hidden @end example
 
-Download the packages relevant to your architecture (currently I have
-access to GNU/Linux machines on x86_64 and i686, so only two for now,
-hopefully more later) from https://gnunet.org/install/.
address@hidden Download the packages relevant to your architecture (currently I 
have
address@hidden access to GNU/Linux machines on x86_64 and i686, so only two for 
now,
address@hidden hopefully more later) from https://gnunet.org/install/.
 
-To install the downloaded package into the directory /foo:
address@hidden To install the downloaded package into the directory /foo:
 
address@hidden
-gnunet-update/bin/gnunet-update install downloaded/package /foo
address@hidden example
address@hidden @example
address@hidden gnunet-update/bin/gnunet-update install downloaded/package /foo
address@hidden @end example
 
-The installer reports the directories into which shared libraries and
-dependencies have been installed. You may need to add the reported shared
-library installation paths to LD_LIBRARY_PATH before you start running any
-installed binaries.
address@hidden The installer reports the directories into which shared 
libraries and
address@hidden dependencies have been installed. You may need to add the 
reported shared
address@hidden library installation paths to LD_LIBRARY_PATH before you start 
running any
address@hidden installed binaries.
 
-Please report bugs at https://gnunet.org/bugs/ under the project
-'gnunet-update'.
address@hidden Please report bugs at https://gnunet.org/bugs/ under the project
address@hidden 'gnunet-update'.
 
 @node Instructions for Microsoft Windows Platforms (Old)
 @subsection Instructions for Microsoft Windows Platforms (Old)

-- 
To stop receiving notification emails like this one, please contact
address@hidden