Changes between Version 62 and Version 63 of AdvancedInstall

Timestamp:

2013-08-08T21:04:41Z (11 years ago)

Author:

zooko

Comment:

use server-relative links instead of absolute

AdvancedInstall

@@ -33 +33 @@
 == Additional !Build/Install Documentation ==
 
-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 [https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev the tahoe-dev mailing list] and ask for help.
+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 [//cgi-bin/mailman/listinfo/tahoe-dev the tahoe-dev mailing list] and ask for help.
 
 
@@ -112 +112 @@
 This disconnected-build operation is supported in two ways. When building
 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
+[//source/tahoe-lafs/deps/tahoe-deps.tar.gz 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
 from its {{{tahoe-deps/}}} directory instead of downloading them from the
@@ -121 +121 @@
 
 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
-current-trunk tarball from https://tahoe-lafs.org/source/tahoe-lafs/tarballs/ ), you
+from [//source/tahoe-lafs/releases/ https://tahoe-lafs.org/source/tahoe-lafs/releases/] , or a continually-generated
+current-trunk tarball from [//source/tahoe-lafs/tarballs/ https://tahoe-lafs.org/source/tahoe-lafs/tarballs/] ), you
 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
@@ -129 +129 @@
 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
-things. The https://tahoe-lafs.org/source/tahoe-lafs/deps/ directory contains
+things. The [//source/tahoe-lafs/deps/ https://tahoe-lafs.org/source/tahoe-lafs/deps/] directory contains
 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.
@@ -164 +164 @@
 === Windows ===
 There used to be an installer for Windows, but we now recommend that Windows
-users just follow the [https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst quickstart instructions].
+users just follow the [//trac/tahoe-lafs/browser/trunk/docs/quickstart.rst quickstart instructions].
 The SMB-based ("WinFUSE") frontend that was provided by the !AllMyData.com
 client is no longer available, since it depended on a closed-source library
@@ -301 +301 @@
 1. 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/ .
 
-2. 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.
+2. Download the latest Tahoe-LAFS release from [//source/tahoe-lafs/releases/ https://tahoe-lafs.org/source/tahoe-lafs/releases/]. Unpack it in a convenient place, such as C:\tahoe-lafs.
 
 3. Open a command prompt and cd to the top of the Tahoe-LAFS tree (e.g. {{{cd \tahoe-lafs}}}).
@@ -324 +324 @@
 2. 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.
 
-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 [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):
+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 [//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):
 
 {{{