tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

move paragraph, clarify what is signed. 

[Imported from Trac: page AdvancedInstall, version 62]
leif 2013-08-08 20:17:36 +00:00
parent 2377ede059
commit 8fd0a6a1a9
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
AdvancedInstall.md

@ -116,12 +116,14 @@ from its `tahoe-deps/` directory instead of downloading them from the
internet. You can also unpack tahoe-deps into the parent directory to share internet. You can also unpack tahoe-deps into the parent directory to share
it between multiple trees. it between multiple trees.
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.
Alternatively, if you are building from a tarball (either a release tarball Alternatively, if you are building from a tarball (either a release tarball
from <https://tahoe-lafs.org/source/tahoe-lafs/releases/> , or a continually-generated from <https://tahoe-lafs.org/source/tahoe-lafs/releases/> , or a continually-generated
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 and is signed with the Tahoe-LAFS Release-Signing Key (`E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A`). in the source tree. The release versions are 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
@ -131,8 +133,6 @@ 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`". 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