Changes between Version 60 and Version 61 of AdvancedInstall


Ignore:
Timestamp:
2013-08-08T20:08:56Z (11 years ago)
Author:
leif
Comment:

update desert island instructions

Legend:

Unmodified
Added
Removed
Modified
  • AdvancedInstall

    v60 v61  
    105105are about to get on an airplane, or you anticipate having poor network
    106106connectivity, or you just don't like the idea of a so-called compile step
    107 using the network (the download step uses !PyPI to figure out where to
     107using the network (the download step connects to PyPI via http to figure out where to
    108108download these libraries from, so you might be concerned that it or one of
    109109the project web pages it references has been modified to point at something
     
    111111
    112112This disconnected-build operation is supported in two ways. When building
    113 from a darcs checkout, you can download the latest "tahoe-deps" bundle from
     113from a git checkout, you can download the latest "tahoe-deps" bundle from
    114114https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz . Unpack this in
    115115your source tree, and the build process will grab any necessary libraries
     
    123123can simply download the -SUMO version of the tarball instead of the regular
    124124one. The "SUMO" tarball includes the current tahoe-deps bundle pre-unpacked
    125 in the source tree.
     125in the source tree and is signed with the Tahoe-LAFS Release-Signing Key ({{{E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A}}}).
    126126
    127127The tahoe-deps bundle is updated every once in a while, as new versions of
     
    130130historical ones, but there should never be a reason to use anything but the
    131131latest. The tahoe-deps bundle contains a README that has a version number.
     132
     133Besides 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}}}".
     134
     135Unfortunately, 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.
    132136
    133137[=#point6]