Changes between Version 61 and Version 62 of AdvancedInstall

Timestamp:

2013-08-08T20:17:36Z (11 years ago)

Author:

leif

Comment:

move paragraph, clarify what is signed.

AdvancedInstall

@@ -118 +118 @@
 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
 from https://tahoe-lafs.org/source/tahoe-lafs/releases/ , or a continually-generated
@@ -123 +125 @@
 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
-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
@@ -132 +134 @@
 
 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.
 
 [=#point6]