From: david-sarah Date: Sun, 12 Dec 2010 22:29:12 +0000 (-0800) Subject: docs/debian.rst: bring description of building dependencies from source up-to-date... X-Git-Url: https://git.rkrishnan.org/pf/content/simplejson/frontends/something?a=commitdiff_plain;h=7be2c73f08717d67d1c85f050392f2ee8f0d03b2;p=tahoe-lafs%2Ftahoe-lafs.git docs/debian.rst: bring description of building dependencies from source up-to-date, and change hostname from allmydata.com to tahoe-lafs.org. --- diff --git a/docs/debian.rst b/docs/debian.rst index a0248f18..71210e59 100644 --- a/docs/debian.rst +++ b/docs/debian.rst @@ -139,12 +139,12 @@ and there are no such source packages in our APT repository. Using Pre-Built Debian Packages =============================== -The allmydata.org site hosts an APT repository with debian packages that are -built after each checkin. `This wiki page -`_ describes this -repository. +The ``tahoe-lafs.org`` site hosts an APT repository with Debian packages that are +built after each checkin. The `DownloadDebianPackages +`_ wiki page +describes this repository. -The allmydata.org APT repository also includes debian packages of support +The ``tahoe-lafs.org`` APT repository also includes Debian packages of support libraries, like Foolscap, zfec, pycryptopp, and everything else you need that isn't already in debian. @@ -172,9 +172,13 @@ will insist upon downloading that specific 0.9.26 version. Since the current release of Nevow is 0.9.31, and 0.9.26 is no longer available for download, this will fail. -The Tahoe source tree currently ships with a directory full of tarballs of -dependent libraries (misc/dependencies/), to enable a "desert-island build". -There are plans to remove these tarballs from the source repository (but -still provide a way to get Tahoe source plus dependencies). This Nevow-0.9.26 --type problem can be mitigated by putting the right dependency tarball in -misc/dependencies/ . +``_ +contains source tarballs for Tahoe's dependent libraries. The Nevow-0.9.26-type +problem can be mitigated by putting the right dependency in ``tahoe-deps``, +or by downloading the "SUMO" distribution of Tahoe-LAFS, which includes all of +these source tarballs. + +If you encounter problems building a dependency from source, +``_ +contains binary (`.egg`) distributions for various OS platforms and versions +of Python.