Update README build info - pee - Pee a password manager;Pee - because you have to...
 (HTM) git clone git://vernunftzentrum.de/pee.git
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) LICENSE
       ---
 (DIR) commit 2d36b79bc40e6a4fb8935d9153d4c5a27248b17d
 (DIR) parent 474de79fca87b69eb65fea91dc5eb791e15f2e64
 (HTM) Author: Christian Kellermann <ckeen@pestilenz.org>
       Date:   Thu,  4 Oct 2018 16:12:20 +0200
       
       Update README build info
       
       Diffstat:
         README.rst                          |      23 ++++++-----------------
       
       1 file changed, 6 insertions(+), 17 deletions(-)
       ---
 (DIR) diff --git a/README.rst b/README.rst
       @@ -20,7 +20,7 @@ If you want to have it available for copy and paste, you should use an external 
        Dependencies
        ------------
        
       -Pee is written in `CHICKEN Scheme`__, the cryptography parts are provided by the tweetnacl egg.
       +Pee is written in `CHICKEN Scheme (version 5)`__, the cryptography parts are provided by the tweetnacl egg.
        The BLAKE2s_ code has been taken verbatim from the reference implementations and is included in the pee source code.
        Other eggs pee depends on are: srfi-1, srfi-4, getopt-long, matchable and stty.
        
       @@ -30,24 +30,13 @@ __ https://www.call-cc.org
        Installing
        ----------
        
       -After unpacking the source build it using the CHICKEN Scheme compiler::
       +After unpacking the source build it using the CHICKEN 5 Scheme compiler::
        
       -  $ chicken-install blob-utils getopt-long matchable stty tweetnacl
       -  $ csc -s -Jc crypto-helper.scm blake2s-ref.c -C -std=c99
       -  $ csc pee.scm
       +  $ ./compile.sh
        
       -Or use the provided .setup file::
       -
       -  $ chicken-install
       -
       -Building a statically linked executable
       ----------------------------------------
       -
       -Sometimes depending on the globally installed CHICKEN runtime is not desireable.
       -To build a statically linked version of Pee use the provided static-compilation.sh shell script.
       -The script will try to fetch all dependencies in the current directory, compiles the necessary units.
       -If all goes well it will clean up afterwards.
       -If not you will have to manually do the clean up.
       +This will create some version info files that get integrated into the executable and calls chicken-install
       +for fetching dependencies and building a static version of pee.
       +The compile script will attempt to clean up if the build fails.
        If you have cloned from the git repo, a git clean -f -d will do that for you.
        
        Using Pee