add a compatiblity table, still needs work
[Imported from Trac: page DownloadDebianPackages, version 15]
parent
3b6ea1fc85
commit
f4b3ac8c9e
|
@ -1,24 +1,58 @@
|
|||
# Debian Packages
|
||||
|
||||
[""Install Tahoe""](http://allmydata.org/source/tahoe/trunk/docs/install.html)
|
||||
tells how to build Tahoe from source.
|
||||
Tahoe is compatible with various releases of Debian/Ubuntu. There are two
|
||||
forms of compatibility: "runs-from-source" and "runs-from-package". Both are
|
||||
pretty easy. If you just want to download a binary package and install it,
|
||||
you'll need the "runs-from-package" kind of compability.
|
||||
|
||||
Precompiled Tahoe packages are also available for Debian-like systems, using
|
||||
recent releases of Debian or Ubuntu. There are also precompiled packages for
|
||||
several of the necessary support libraries which are not already in the
|
||||
debian distribution:
|
||||
## Compability
|
||||
|
||||
* debian "etch": Tahoe and support libraries
|
||||
* debian "lenny" (not yet released): use "etch"
|
||||
* debian "sid": support libaries only, use "etch" for the Tahoe package
|
||||
(note, the contents of this table have not yet been verified)
|
||||
|
||||
* ubuntu "dapper": not supported since tahoe-0.4.0 (July 2007)
|
||||
* ubuntu "edgy": Tahoe and support libraries
|
||||
* ubuntu "feisty": Tahoe and support libraries
|
||||
* ubuntu "gutsy": Tahoe and support libraries
|
||||
* ubuntu "hardy": Tahoe and support libraries
|
||||
| | | | |
|
||||
|---|---|---|---|
|
||||
|platform|runs-from-source|runs-from-package|support packages available|
|
||||
|Debian "etch"|yes|?|yes|
|
||||
|Debian "lenny"|yes|yes|yes (use etch)|
|
||||
|Debian "sid"|yes|yes|yes|
|
||||
|Ubuntu "dapper"|yes|no|no|
|
||||
|Ubuntu "edgy"|yes|?|yes|
|
||||
|Ubuntu "feisty"|yes|no?|yes|
|
||||
|Ubuntu "gutsy"|yes|no (#149)|yes|
|
||||
|Ubuntu "hardy"|yes|yes|yes|
|
||||
|Ubuntu "intrepid"|yes|yes|yes|
|
||||
|
||||
allmydata.org hosts an APT repository at <http://allmydata.org/debian/> . To
|
||||
"runs-from-source" means that it is possible to take a Tahoe source tree
|
||||
(either from a downloaded tarball or from a darcs checkout) and run
|
||||
`python setup.py build` on it, then run `./bin/tahoe` to use it. This
|
||||
approach is described on the
|
||||
[http://allmydata.org/source/tahoe/trunk/docs/install.html ""Install Tahoe""]
|
||||
page.
|
||||
|
||||
(if you can run-from-source, you should also be able to use
|
||||
`python setup.py install` to copy tahoe into /usr/bin/tahoe (or
|
||||
whatever is appropriate for your system), so you can use it after the source
|
||||
tree has been removed. However, using `setup.py install` will modify your
|
||||
/usr partition without the knowledge of the Debian package-management tools,
|
||||
making it more difficult to coordinate dependencies with other packages,
|
||||
and making it difficult to remove Tahoe later)
|
||||
|
||||
"run-from-package" means that it is possible to download a pre-built Tahoe
|
||||
binary package from the APT repository on allmydata.org (as well as packages
|
||||
for any dependencies that are not otherwise available in the Debian/Ubuntu
|
||||
release), and then run /usr/bin/tahoe to use that installation. It also means
|
||||
that these .deb packages can be built from a source tree on those platforms
|
||||
(which the allmydata.org buildbot does automatically, to populate the APT
|
||||
repository).
|
||||
|
||||
"support packages available" means that the allmydata.org APT repository has
|
||||
debian packages available for several of the libraries which Tahoe requires
|
||||
(those which are not already in the debian release). This might make it
|
||||
easier to build Tahoe from source (fewer things to download).
|
||||
|
||||
== Downloading/Installing Binary Packages ==
|
||||
|
||||
allmydata.org hosts an APT repository at http://allmydata.org/debian/ . To
|
||||
install packages from this repository, add the following lines to your
|
||||
`/etc/apt/sources.list`, replacing the word `$DIST` with one of
|
||||
`etch`, `sid`, `edgy`, `feisty`, or `gutsy` as
|
||||
|
|
Loading…
Reference in a new issue