These instructions are I2P specific, for generic documentation see Tahoe-LAFS Docs.
You should have already installed and be familiar with I2P.
We will use the tahoe-i2p-install script created by smeghead for the actual installation.
*BSD/Linux/Mac OS X/Solaris:
Bash or Zsh, GCC, Python 2.5 or 2.6 (not 3.x), Wget. Development headers for Python and OpenSSL. You need about 100MB of free disk space to install.
Windows:
Unsupported, but same as above plus MinGW or Cygwin and probably lots of spit, glue, duct tape and virgin sacrifices. If you make it work please contribute your changes to this script's maintainer (by doing so you agree to release the work into the public domain) and if they're sane enough they'll be included in the next release.
If the --fetch-patches-i2p option is used then I2P must be installed and running locally with its HTTP Proxy enabled, and the base directory of your I2P installation must be in the PATH environment variable.
Create a directory for the installation, we suggest ~/tahoe
$ mkdir ~/tahoe
$ cd ~/tahoe
Download the script: tahoe-i2p-install-v1.2.7.sh
Make it executable
$ chmod u+x tahoe-i2p-install-v.1.2.7.sh
Show usage information
$ ./tahoe-i2p-install --help
Perform the actual installation (see usage information from above for additional options)
$ ./tahoe-i2p-install
You can safely ignore most C / C++ compilation warnings. If you get any errors, please see appendix A.
As suggested by the script, update your environment with PATH and PYTHONPATH.
Verify the installation
$ tahoe --version
This will print the version of Tahoe and depending libraries.
If everything went well, you are now the proud owner of Tahoe-LAFS for I2P.
Next will be the configuration of your node(s) specifically for I2P. Continue your journey with the usage manual.
error: Python.h: No such file or directory
You need to install the Python development headers. In Linux distributions this is usually the python-dev (Debian / Ubuntu) or python-devel (RedHat / Fedora) package.
error: openssl/ssl.h: No such file or directory
You need to install the OpenSSL development headers. In Linux distributions this is usually the libssl-dev (Debian / Ubuntu) or openssl-devel (RedHat / Fedora) package.