Changes between Version 59 and Version 60 of AdvancedInstall


Ignore:
Timestamp:
2013-08-08T17:37:03Z (12 years ago)
Author:
leif
Comment:

s/http:/https:/ all links except python.org which doesn't do https

Legend:

Unmodified
Added
Removed
Modified

  • AdvancedInstall

    v59 v60  
    3333== Additional !Build/Install Documentation ==
    3434
    35 The quick start docs in [source:docs/quickstart.rst] are sufficient to get Tahoe-LAFS running on all platforms. This wiki page is ''only'' for advanced, optional installation features and you should not read this page if all you want is to get Tahoe-LAFS running. If you have trouble getting it to work by following [source:docs/quickstart.rst] then please write to [http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev the tahoe-dev mailing list] and ask for help.
     35The quick start docs in [source:docs/quickstart.rst] are sufficient to get Tahoe-LAFS running on all platforms. This wiki page is ''only'' for advanced, optional installation features and you should not read this page if all you want is to get Tahoe-LAFS running. If you have trouble getting it to work by following [source:docs/quickstart.rst] then please write to [https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev the tahoe-dev mailing list] and ask for help.
    3636
    3737
    … …  
    6060`zope.interface: 3.5.0, simplejson: 2.0.7, pyutil: 1.3.30, zbase32: 1.1.1, allmydata-tahoe: 1.2.0-r3353, pyOpenSSL: 0.7, Twisted: 8.1.0-r25700, Nevow: 0.9.33-r17166, foolscap: 0.3.2, zfec: 1.4.2, pycryptopp: 0.5.12, argparse: 0.8.0, setuptools: 0.6c10dev`
    6161
    62 Prior to Tahoe-LAFS v1.9.0, users running on Microsoft Windows also needed to manually install [http://sourceforge.net/projects/pywin32 pywin32]. This should no longer be needed.
     62Prior to Tahoe-LAFS v1.9.0, users running on Microsoft Windows also needed to manually install [https://sourceforge.net/projects/pywin32 pywin32]. This should no longer be needed.
    6363
    6464[=#point4]
    … …  
    112112This disconnected-build operation is supported in two ways. When building
    113113from a darcs checkout, you can download the latest "tahoe-deps" bundle from
    114 http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz . Unpack this in
     114https://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
    116116from its {{{tahoe-deps/}}} directory instead of downloading them from the
    … …  
    119119
    120120Alternatively, if you are building from a tarball (either a release tarball
    121 from http://tahoe-lafs.org/source/tahoe-lafs/releases/ , or a continually-generated
    122 current-trunk tarball from http://tahoe-lafs.org/source/tahoe-lafs/tarballs/ ), you
     121from https://tahoe-lafs.org/source/tahoe-lafs/releases/ , or a continually-generated
     122current-trunk tarball from https://tahoe-lafs.org/source/tahoe-lafs/tarballs/ ), you
    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
    … …  
    127127The tahoe-deps bundle is updated every once in a while, as new versions of
    128128the dependent libraries are released, or as Tahoe becomes dependent upon new
    129 things. The http://tahoe-lafs.org/source/tahoe-lafs/deps/ directory contains
     129things. The https://tahoe-lafs.org/source/tahoe-lafs/deps/ directory contains
    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.
    … …  
    160160=== Windows ===
    161161There used to be an installer for Windows, but we now recommend that Windows
    162 users just follow the [http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst quickstart instructions].
     162users just follow the [https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst quickstart instructions].
    163163The SMB-based ("WinFUSE") frontend that was provided by the !AllMyData.com
    164164client is no longer available, since it depended on a closed-source library
    … …  
    208208that aren't already in Debian proper.
    209209
    210 It is also possible to create a binary distribution using [http://pypi.python.org/pypi/bbfreeze bb-freeze].
     210It is also possible to create a binary distribution using [https://pypi.python.org/pypi/bbfreeze bb-freeze].
    211211Install bb-freeze, then in the root of a Tahoe source tree with full path
    212212{{{<tahoedir>}}}, on Windows do:
    … …  
    2972971. Download and install Python 2.7.3 (the x86 or x86-64 MSI installer link) from http://www.python.org/getit/releases/2.7.3/ .
    298298
    299 2. Download the latest Tahoe-LAFS release from http://tahoe-lafs.org/source/tahoe-lafs/releases/. Unpack it in a convenient place, such as C:\tahoe-lafs.
     2992. Download the latest Tahoe-LAFS release from https://tahoe-lafs.org/source/tahoe-lafs/releases/. Unpack it in a convenient place, such as C:\tahoe-lafs.
    300300
    3013013. Open a command prompt and cd to the top of the Tahoe-LAFS tree (e.g. {{{cd \tahoe-lafs}}}).
    … …  
    316316The build or install steps could result in an error that says a compiler is needed. If this happens and you are using Python 2.7, it is a packaging bug that should be reported to the tahoe-dev list. If you are using a different version of Python or want to compile the C/C++ components yourself, install the MinGW C/C++ compiler as follows (this only works for 32-bit Windows):
    317317
    318 1. Download and install MinGW from http://sourceforge.net/projects/mingw/files/ (the main installer linked from the big green download button). The installer will prompt you for what components to install. You need the base components plus g++.
     3181. Download and install MinGW from https://sourceforge.net/projects/mingw/files/ (the main installer linked from the big green download button). The installer will prompt you for what components to install. You need the base components plus g++.
    319319
    3203202. Early versions of 5.1.x of MinGW had a bug in the bundled Gnu assembler. If typing "{{{as --version}}}" at the command line gives "{{{GNU assembler (GNU Binutils) 2.20}}}", then you have an affected version. To fix this, download an upgrade to a newer version of MinGW which has {{{GNU assembler (GNU Binutils) 2.20.51.20100613}}} or later.
    321321
    322 3. Configure distutils to use MinGW. If you have another C/C++ compiler installed, such as the cygwin one, distutils may default to using it instead of the mingw one. To configure distutils to use mingw32, create a file called [http://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AdvancedInstall/distutils.cfg distutils.cfg] in {{{C:\Python27\lib\distutils}}}, and put in that file (you may also need to use the script from [http://mail.python.org/pipermail/python-dev/2004-January/041676.html this email] in order to "register" the mingw compiler):
     3223. Configure distutils to use MinGW. If you have another C/C++ compiler installed, such as the cygwin one, distutils may default to using it instead of the mingw one. To configure distutils to use mingw32, create a file called [https://tahoe-lafs.org/trac/tahoe-lafs/raw-attachment/wiki/AdvancedInstall/distutils.cfg distutils.cfg] in {{{C:\Python27\lib\distutils}}}, and put in that file (you may also need to use the script from [https://mail.python.org/pipermail/python-dev/2004-January/041676.html this email] in order to "register" the mingw compiler):
    323323
    324324{{{
    … …  
    336336==== How do I make it run as a Windows service? ====
    337337
    338 http://agiletesting.blogspot.com/2005/09/running-python-script-as-windows.html
     338https://agiletesting.blogspot.com/2005/09/running-python-script-as-windows.html
    339339
    340340[=#point9.4.3]