update desert island instructions
[Imported from Trac: page AdvancedInstall, version 61]
parent
7c41584c77
commit
2377ede059
|
@ -103,13 +103,13 @@ Tahoe-LAFS will download and install most of the libraries it requires when you
|
||||||
run "`python setup.py build`". You might want to pre-download these libraries: perhaps you
|
run "`python setup.py build`". You might want to pre-download these libraries: perhaps you
|
||||||
are about to get on an airplane, or you anticipate having poor network
|
are about to get on an airplane, or you anticipate having poor network
|
||||||
connectivity, or you just don't like the idea of a so-called compile step
|
connectivity, or you just don't like the idea of a so-called compile step
|
||||||
using the network (the download step uses !PyPI to figure out where to
|
using the network (the download step connects to PyPI via http to figure out where to
|
||||||
download these libraries from, so you might be concerned that it or one of
|
download these libraries from, so you might be concerned that it or one of
|
||||||
the project web pages it references has been modified to point at something
|
the project web pages it references has been modified to point at something
|
||||||
malicious).
|
malicious).
|
||||||
|
|
||||||
This disconnected-build operation is supported in two ways. When building
|
This disconnected-build operation is supported in two ways. When building
|
||||||
from a darcs checkout, you can download the latest "tahoe-deps" bundle from
|
from a git checkout, you can download the latest "tahoe-deps" bundle from
|
||||||
<https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz> . Unpack this in
|
<https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz> . Unpack this in
|
||||||
your source tree, and the build process will grab any necessary libraries
|
your source tree, and the build process will grab any necessary libraries
|
||||||
from its `tahoe-deps/` directory instead of downloading them from the
|
from its `tahoe-deps/` directory instead of downloading them from the
|
||||||
|
@ -121,7 +121,7 @@ from <https://tahoe-lafs.org/source/tahoe-lafs/releases/> , or a continually-gen
|
||||||
current-trunk tarball from <https://tahoe-lafs.org/source/tahoe-lafs/tarballs/> ), you
|
current-trunk tarball from <https://tahoe-lafs.org/source/tahoe-lafs/tarballs/> ), you
|
||||||
can simply download the -SUMO version of the tarball instead of the regular
|
can simply download the -SUMO version of the tarball instead of the regular
|
||||||
one. The "SUMO" tarball includes the current tahoe-deps bundle pre-unpacked
|
one. The "SUMO" tarball includes the current tahoe-deps bundle pre-unpacked
|
||||||
in the source tree.
|
in the source tree and is signed with the Tahoe-LAFS Release-Signing Key (`E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A`).
|
||||||
|
|
||||||
The tahoe-deps bundle is updated every once in a while, as new versions of
|
The tahoe-deps bundle is updated every once in a while, as new versions of
|
||||||
the dependent libraries are released, or as Tahoe becomes dependent upon new
|
the dependent libraries are released, or as Tahoe becomes dependent upon new
|
||||||
|
@ -129,6 +129,10 @@ things. The <https://tahoe-lafs.org/source/tahoe-lafs/deps/> directory contains
|
||||||
historical ones, but there should never be a reason to use anything but the
|
historical ones, but there should never be a reason to use anything but the
|
||||||
latest. The tahoe-deps bundle contains a README that has a version number.
|
latest. The tahoe-deps bundle contains a README that has a version number.
|
||||||
|
|
||||||
|
Besides tahoe-deps, you'll also need a C++ compiler and Python headers. These requirements can be satisfied on a Debian system with "`apt-get install build-essential python-dev`".
|
||||||
|
|
||||||
|
Unfortunately, setup.py will still try to connect to the internet even if the `tahoe-deps` directory exists, and if it succeeds and finds newer versions of any dependencies it will likely still download and run them (without any integrity checking). So, for a truly offline build, you currently must run setup.py in an environment where it cannot reach the internet. See #2055.
|
||||||
|
|
||||||
<a name="point6"></a>
|
<a name="point6"></a>
|
||||||
## Installing Outside The Source Tree
|
## Installing Outside The Source Tree
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue