Changes between Version 43 and Version 44 of DownloadDebianPackages


Ignore:
Timestamp:
2010-04-03T19:47:50Z (15 years ago)
Author:
zooko
Comment:

change name to "Tahoe-LAFS" and change "support" to "dependency" in most instances

Legend:

Unmodified
Added
Removed
Modified

  • DownloadDebianPackages

    v43 v44  
    22= Debian Packages =
    33
    4 Tahoe is compatible with various releases of Debian/Ubuntu. There are two
     4Tahoe-LAFS is compatible with various releases of !Debian/Ubuntu. There are two
    55forms of compatibility: "apt-get installable" and "runs-from-source". Both
    66are pretty easy. If you just want to download a binary package and install
    … …  
    1111(note, the contents of this table have not yet been verified)
    1212
    13 ||platform||apt-get installable||deb buildable||tahoe deb available||support debs available||runs-from-source||included in distribution||priority||
    14 ||Debian 3.1 "sarge"||no||no||no||no||?|| || ||
     13||platform||apt-get installable||deb buildable||tahoe-lafs deb available||dependency debs available||runs-from-source||included in distribution||priority||
     14||Debian 3.1 "sarge"||no||no||no||no|||?||no|| ||
    1515||Debian 4.0 "etch" i386||no||yes||yes||no (missing pycryptopp)||[http://allmydata.org/buildbot/waterfall?show_events=false&builder=etch yes]|| || ||
    1616||Debian 5.0 "lenny" i386||yes?||yes||yes (use etch)||yes (use etch for zfec/foolscap)||yes?|| ||*||
    … …  
    3434||Ubuntu 10.04 "lucid" amd64|| ? || ? || ? || ? || ? ||Tahoe-LAFS v1.6.1||*||
    3535
    36 "apt-get installable" means that it is possible to download a pre-built Tahoe
     36"apt-get installable" means that it is possible to download a pre-built Tahoe-LAFS
    3737binary package from the APT repository on allmydata.org (as well as packages
    38 for any dependencies that are not otherwise available in the Debian/Ubuntu
     38for any dependencies that are not otherwise available in the !Debian/Ubuntu
    3939release), and then run /usr/bin/tahoe to use that installation. Follow the
    4040instructions below to edit your /etc/apt/sources.list file. "apt-get
    41 installable" = ("tahoe deb available" AND "support debs available").
    42 
    43 "deb buildable" means that a tahoe .deb package can be built from a source
    44 tree. "tahoe deb available" means the allmydata.org buildbot does this
     41installable" = ("tahoe-lafs deb available" AND "dependency debs available").
     42
     43"deb buildable" means that a tahoe-lafs .deb package can be built from a source
     44tree. "tahoe-lafs deb available" means the allmydata.org buildbot does this
    4545automatically, to populate the APT repository. We do not have automatic
    4646builders for all platforms, so there are holes in this table.
    4747
    48 "support debs available" means that the allmydata.org APT repository has
    49 debian packages available for everything that Tahoe needs (those which are
     48"dependency debs available" means that the allmydata.org APT repository has
     49debian packages available for everything that Tahoe-LAFS needs (those which are
    5050not already in that debian release: over time, many of the packages are being
    5151added to debian proper, and no longer need to be hosted here). This is
    52 required to make tahoe be "apt-get installable" on any given platform.
    53 
    54 "runs-from-source" means that it is possible to take a Tahoe source tree
     52required to make Tahoe-LAFS be "apt-get installable" on any given platform.
     53
     54"runs-from-source" means that it is possible to take a Tahoe-LAFS source tree
    5555(either from a downloaded tarball or from a darcs checkout) and run
    5656{{{python setup.py build}}} on it, then run {{{./bin/tahoe}}} to use it. This approach
    5757is described on the
    58 [http://allmydata.org/source/tahoe/trunk/docs/install.html ""Install Tahoe""]
     58[http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/install.html ""Install Tahoe-LAFS""]
    5959page. The allmydata.org buildbot automatically tests run-from-source on most
    6060debian platforms.
    … …  
    8282apt-get will automatically acquire other dependency packages from the same
    8383repository (including {{{foolscap}}}, {{{zfec}}}, {{{pycryptopp}}}, and
    84 others). The "tahoe" section contains the Tahoe debian packages, while the
    85 "main" section contains the support libraries.
     84others). The "tahoe" section contains the Tahoe-LAFS debian packages, while the
     85"main" section contains the dependency libraries.
    8686
    8787Note that these {{{allmydata-tahoe}}} packages are generated each time the
    … …  
    8989available. The usual warnings about no guarantees apply: it might cause your
    9090computer to catch fire, might steal your dog, etc. In the future, we will add
    91 a section to the repository that only contains released versions of Tahoe,
     91a section to the repository that only contains released versions of Tahoe-LAFS,
    9292probably called "tahoe-releases". The packages in this section should be more
    9393stable than the bleeding-edge packages in the "tahoe" section.
    9494
    95 After installing see the [http://allmydata.org/source/tahoe/trunk/docs/running.html docs/running.html] for how to use it.
     95After installing see the [http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/running.html docs/running.html] for how to use it.
    9696
    9797There are no pre-built packages available for dapper or sarge, as these
    … …  
    123123Nevow (0.7.0) which shipped with edgy is broken (ubuntu bug
    124124[https://bugs.launchpad.net/ubuntu/+source/nevow/+bug/61423 #61423]),
    125 preventing the tahoe node's webserver from running. The symptom is an
     125preventing the Tahoe-LAFS node's webserver from running. The symptom is an
    126126exception at node startup that looks like this:
    127127
    … …  
    151151
    152152If your platform is not listed as "apt-get installable" above, or if you
    153 don't have root access, or simply want to run Tahoe without installing it,
     153don't have root access, or simply want to run Tahoe-LAFS without installing it,
    154154you can use the regular run-from-source procedure described in
    155 http://allmydata.org/source/tahoe/trunk/docs/install.html . As long as you
     155http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/install.html . As long as you
    156156run this as a normal (non-root) user and don't use "sudo" at any time, this
    157157will not modify your system and will not interfere with the normal apt-get
    158158tools. Building from a source tree and then symlinking {{{~/bin/tahoe}}} to
    159 the tree's {{{bin/tahoe}}} executable is a convenient way to use Tahoe
     159the tree's {{{bin/tahoe}}} executable is a convenient way to use Tahoe-LAFS
    160160without installing it to your {{{/usr}}} directory.
    161161
    162 Many of Tahoe's build dependencies can be satisfied by first installing
    163 certain debian packages, and the Tahoe build process will download and build
     162Many of Tahoe-LAFS's build dependencies can be satisfied by first installing
     163certain debian packages, and the Tahoe-LAFS build process will download and build
    164164many of the others. Please see source:docs/debian.txt for details about
    165 building Tahoe on a debian-based system. The following text is a copy of
     165building Tahoe-LAFS on a debian-based system. The following text is a copy of
    166166source:docs/debian.txt .
    167167
    168 The Tahoe build process will download and install many of its dependencies
     168The Tahoe-LAFS build process will download and install many of its dependencies
    169169when you run {{{make}}} or {{{setup.py build}}}. The base set of
    170170functionality that it cannot build on its own are provided by the following
    … …  
    186186"fakeroot" package.
    187187
    188 To actually run a Tahoe node from a debian package, you will need the following
    189 supporting libraries installed. (again, the authoritative list of packages
     188To actually run a Tahoe-LAFS node from a debian package, you will need the following
     189dependencies installed. (again, the authoritative list of packages
    190190is in the {{{Depends:}}} clause of
    191191[source:misc/sid/debian/control misc/sid/debian/control])
    … …  
    200200 * python-pycryptopp
    201201
    202 Even if you don't intend to create a Tahoe .deb package, you can install the
     202Even if you don't intend to create a Tahoe-LAFS .deb package, you can install the
    203203supporting libraries from debian packages to reduce the build-time
    204 download-and-compile work. The Tahoe build process will use any pre-installed
     204download-and-compile work. The Tahoe-LAFS build process will use any pre-installed
    205205libraries it can find, and will download+build everything else.
    206206
    … …  
    208208
    209209Please see source:docs/debian.txt for details about building your own debian
    210 packages from a Tahoe source tree. You will need to install the packages
     210packages from a Tahoe-LAFS source tree. You will need to install the packages
    211211described above, including the "devscripts" and "fakeroot" packages, and you
    212212will use the {{{make deb-$PLATFORM-head}}} target.
    213213
    214 Note that this is entirely optional. Tahoe will run just fine from a source
     214Note that this is entirely optional. Tahoe-LAFS will run just fine from a source
    215215tree: creating a debian package is merely a convenience for sysadmins to help
    216 them manage large numbers of Tahoe nodes with established tools like apt-get.
     216them manage large numbers of Tahoe-LAFS nodes with established tools like apt-get.