docs

doc/installation_manual.md

@@ -15,7 +15,7 @@ to download both the binaries and/or pull containers from repositories.
 
 ## 2. USER INSTALLATION
 
-### 2.1. INSTALL LATEST UDOCKER DIRECTLY FROM GITHUB
+### 2.1. INSTALL LATEST VERSIONS DIRECTLY FROM GITHUB
 
 Just download and execute the udocker and the installation will be performed
 automatically.
@@ -43,37 +43,35 @@ From the development branch:
   ./udocker install
 ```
 
-### 2.2. INSTALL FROM OFFICIAL INDIGO REPOSITORIES
+### 2.2. INSTALL FROM INDIGO-DATACLOUD REPOSITORIES
 <!--
 -->
 The official release of udocker is available from the INDIGO-DataCloud
 repository at `http://repo.indigo-datacloud.eu/` where is made available
 as a tarball to be deployed by the end user.
 
 This installation method contains statically compiled binaries and is built
-to be used across different hosts and OS distributions.
+to be used across different hosts and OS distributions. Please check the
+repositories for the latest release.
 
-Install or upgrade of udocker v1.1.1 or higher released by INDIGO-DataCloud:
+Install or upgrade of udocker v1.1.0 or higher released by INDIGO-DataCloud:
 
 ```
-  curl http://repo.indigo-datacloud.eu/repository/indigo/2/centos7/x86_64/tgz/udocker-1.1.1.tar.gz > udocker-tarball.tgz
+  curl http://repo.indigo-datacloud.eu/repository/indigo/2/centos7/x86_64/tgz/udocker-1.1.0.tar.gz > udocker-tarball.tgz
   export UDOCKER_TARBALL=$(pwd)/udocker-tarball.tgz
   tar xzvf $UDOCKER_TARBALL udocker
   ./udocker install
-  mv ./udocker $HOME   # move the executable to your preferred location for binaries
+  mv ./udocker $HOME/bin/   # move the executable to your preferred location for binaries
 ```
 
-When using the setup.py provided in the release use:
+When using the setup.py provided in the release after downloading use:
 
 ```
-  mkdir /tmp/somedir
-  cd /tmp/somedir
-  curl http://repo.indigo-datacloud.eu/repository/indigo/2/centos7/x86_64/tgz/udocker-1.1.1.tar.gz | tar xzvf -
-  python setup.py install --home /home/USER/bin
+  python setup.py install --home $HOME/bin/
 ```
 
 
-### 2.3. OBTAINING THE URL OF THE LATEST TARBALL
+### 2.3. OBTAINING THE URL OF THE TARBALL
 
 The udocker installation tarball mentioned in section 2.2 can be obtained using the 
 following method. First download udocker. Second use udocker itself to display the
@@ -84,7 +82,11 @@ contain several URLs pointing to mirrors.
   ./udocker version
 ```
 
-Third, pick one URL and download the tarball using tools such as curl or wget.
+Then, pick one URL and download the tarball using tools such as curl or wget.
+By using a previously downloaded tarball and the UDOCKER_TARBALL environment variable 
+as explained in section 2.2, udocker can be deployed without having to downloaded it 
+everytime from the official repositories. The UDOCKER_TARBALL environment variable
+can also be pointed to an http or https URL.
 
 ### 2.4. FORCE REINSTALLATION
 
@@ -105,20 +107,21 @@ systems use the tarball installation methods described above in section 2.
 RPMs are provided at http://repo.indigo-datacloud.eu
 
 ```
-  rpm -i udocker-1.1.1-1.noarch.rpm \
-         udocker-preng-1.1.1-1.x86_64.rpm \
-         udocker-freng-1.1.1-1.x86_64.rpm
+  rpm -i udocker-1.1.X-1.noarch.rpm \
+         udocker-preng-1.1.X-1.x86_64.rpm \
+         udocker-freng-1.1.X-1.x86_64.rpm
 ```
 
 DEBs are provided at http://repo.indigo-datacloud.eu
 
 ```
-  dpkg -i udocker_1.1.1-1_all.deb \
-          udocker-preng_1.1.1-1_amd64.deb \
-          udocker-freng_1.1.1-1_amd64.deb \
-          udocker-rceng_1.1.1-1_amd64.deb
+  dpkg -i udocker_1.1.X-1_all.deb \
+          udocker-preng_1.1.X-1_amd64.deb \
+          udocker-freng_1.1.X-1_amd64.deb \
+          udocker-rceng_1.1.X-1_amd64.deb
 ```
 Check the INDIGO-DataCloud repository for the latest versions and supported distributions.
+Replace `X` in the examples with the latest version.
 Notice that the rc engine (udocker-rceng) package is only available for Ubuntu 14 and 16.
 
 ## 4. SYSTEM INSTALLATION WITH ANSIBLE AND PYTHON
@@ -241,4 +244,3 @@ Example of the udocker.conf syntax:
   verbose_level = 5
 ```
 
-