| 15 | | * ubuntu "dapper": not supported since tahoe-0.4.0 (July 2007) |
| 16 | | * ubuntu "edgy": Tahoe and support libraries |
| 17 | | * ubuntu "feisty": Tahoe and support libraries |
| 18 | | * ubuntu "gutsy": Tahoe and support libraries |
| 19 | | * ubuntu "hardy": Tahoe and support libraries |
| | 12 | ||platform||runs-from-source||runs-from-package||support packages available|| |
| | 13 | ||Debian "etch"||yes||?||yes|| |
| | 14 | ||Debian "lenny"||yes||yes||yes (use etch)|| |
| | 15 | ||Debian "sid"||yes||yes||yes|| |
| | 16 | ||Ubuntu "dapper"||yes||no||no|| |
| | 17 | ||Ubuntu "edgy"||yes||?||yes|| |
| | 18 | ||Ubuntu "feisty"||yes||no?||yes|| |
| | 19 | ||Ubuntu "gutsy"||yes||no (#149)||yes|| |
| | 20 | ||Ubuntu "hardy"||yes||yes||yes|| |
| | 21 | ||Ubuntu "intrepid"||yes||yes||yes|| |
| | 22 | |
| | 23 | "runs-from-source" means that it is possible to take a Tahoe source tree |
| | 24 | (either from a downloaded tarball or from a darcs checkout) and run |
| | 25 | {{{python setup.py build}}} on it, then run {{{./bin/tahoe}}} to use it. This |
| | 26 | approach is described on the |
| | 27 | [http://allmydata.org/source/tahoe/trunk/docs/install.html ""Install Tahoe""] |
| | 28 | page. |
| | 29 | |
| | 30 | (if you can run-from-source, you should also be able to use |
| | 31 | {{{python setup.py install}}} to copy tahoe into /usr/bin/tahoe (or |
| | 32 | whatever is appropriate for your system), so you can use it after the source |
| | 33 | tree has been removed. However, using {{{setup.py install}}} will modify your |
| | 34 | /usr partition without the knowledge of the Debian package-management tools, |
| | 35 | making it more difficult to coordinate dependencies with other packages, |
| | 36 | and making it difficult to remove Tahoe later) |
| | 37 | |
| | 38 | "run-from-package" means that it is possible to download a pre-built Tahoe |
| | 39 | binary package from the APT repository on allmydata.org (as well as packages |
| | 40 | for any dependencies that are not otherwise available in the Debian/Ubuntu |
| | 41 | release), and then run /usr/bin/tahoe to use that installation. It also means |
| | 42 | that these .deb packages can be built from a source tree on those platforms |
| | 43 | (which the allmydata.org buildbot does automatically, to populate the APT |
| | 44 | repository). |
| | 45 | |
| | 46 | "support packages available" means that the allmydata.org APT repository has |
| | 47 | debian packages available for several of the libraries which Tahoe requires |
| | 48 | (those which are not already in the debian release). This might make it |
| | 49 | easier to build Tahoe from source (fewer things to download). |
| | 50 | |
| | 51 | == Downloading/Installing Binary Packages == |