From f879313842dfa9e5ebdf132768bf324eed2380fe Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 8 Aug 2013 21:04:41 +0000
Subject: [PATCH] use server-relative links instead of absolute
[Imported from Trac: page AdvancedInstall, version 63]
---
AdvancedInstall.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/AdvancedInstall.md b/AdvancedInstall.md
index 9878e16..6031f95 100644
--- a/AdvancedInstall.md
+++ b/AdvancedInstall.md
@@ -31,7 +31,7 @@ see also [Packaging](Packaging) and [OSPackages](OSPackages)
## 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 [the tahoe-dev mailing list](https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev) 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.
*Zooko writing: I do not take any responsibility for the contents of this page -- [AdvancedInstall](AdvancedInstall). In my opinion it contains some bits of bad advice and obsolete statements. I don't take the time to monitor or edit this page. I would advise you to follow source:docs/quickstart.rst instead, and if that doesn't work then email the tahoe-dev list for help.*
@@ -110,7 +110,7 @@ malicious).
This disconnected-build operation is supported in two ways. When building
from a git checkout, you can download the latest "tahoe-deps" bundle from
- . Unpack this in
+[//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
internet. You can also unpack tahoe-deps into the parent directory to share
@@ -119,15 +119,15 @@ 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 , or a continually-generated
-current-trunk tarball from ), you
+from [//source/tahoe-lafs/releases/ ] , or a continually-generated
+current-trunk tarball from [//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
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 dependent libraries are released, or as Tahoe becomes dependent upon new
-things. The directory contains
+things. The [//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.
@@ -162,7 +162,7 @@ details.
### Windows
There used to be an installer for Windows, but we now recommend that Windows
-users just follow the [quickstart instructions](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst).
+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
for which no open-source replacement was available. If you are interested in
@@ -298,7 +298,7 @@ Note that this assumes that you install Python in the default location (C:\Pytho
1. Download and install Python 2.7.3 (the x86 or x86-64 MSI installer link) from .
-2. Download the latest Tahoe-LAFS release from . Unpack it in a convenient place, such as C:\tahoe-lafs.
+2. Download the latest Tahoe-LAFS release from [//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`).
@@ -321,7 +321,7 @@ The build or install steps could result in an error that says a compiler is need
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):
```
[build]