s/http:/https:/ all links except python.org which doesn't do https
[Imported from Trac: page AdvancedInstall, version 60]
parent
30031cfd44
commit
7c41584c77
|
@ -31,7 +31,7 @@ see also [Packaging](Packaging) and [OSPackages](OSPackages)
|
|||
<a name="point1"></a>
|
||||
## 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](http://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 [the tahoe-dev mailing list](https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev) 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.*
|
||||
|
@ -58,7 +58,7 @@ This isn't a complete list of dependencies though, because some of those package
|
|||
|
||||
`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`
|
||||
|
||||
Prior to Tahoe-LAFS v1.9.0, users running on Microsoft Windows also needed to manually install [pywin32](http://sourceforge.net/projects/pywin32). This should no longer be needed.
|
||||
Prior to Tahoe-LAFS v1.9.0, users running on Microsoft Windows also needed to manually install [pywin32](https://sourceforge.net/projects/pywin32). This should no longer be needed.
|
||||
|
||||
<a name="point4"></a>
|
||||
## Overview
|
||||
|
@ -110,22 +110,22 @@ malicious).
|
|||
|
||||
This disconnected-build operation is supported in two ways. When building
|
||||
from a darcs checkout, you can download the latest "tahoe-deps" bundle from
|
||||
<http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz> . Unpack this in
|
||||
<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
|
||||
internet. You can also unpack tahoe-deps into the parent directory to share
|
||||
it between multiple trees.
|
||||
|
||||
Alternatively, if you are building from a tarball (either a release tarball
|
||||
from <http://tahoe-lafs.org/source/tahoe-lafs/releases/> , or a continually-generated
|
||||
current-trunk tarball from <http://tahoe-lafs.org/source/tahoe-lafs/tarballs/> ), you
|
||||
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
|
||||
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 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 <http://tahoe-lafs.org/source/tahoe-lafs/deps/> directory contains
|
||||
things. The <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.
|
||||
|
||||
|
@ -158,7 +158,7 @@ details.
|
|||
<a name="point6.4"></a>
|
||||
### Windows
|
||||
There used to be an installer for Windows, but we now recommend that Windows
|
||||
users just follow the [quickstart instructions](http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst).
|
||||
users just follow the [quickstart instructions](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst).
|
||||
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
|
||||
|
@ -206,7 +206,7 @@ but it will not include any code from them. The allmydata.org APT repository
|
|||
(see DownloadDebianPackages for details) has packages for the dependencies
|
||||
that aren't already in Debian proper.
|
||||
|
||||
It is also possible to create a binary distribution using [http://pypi.python.org/pypi/bbfreeze bb-freeze].
|
||||
It is also possible to create a binary distribution using [https://pypi.python.org/pypi/bbfreeze bb-freeze].
|
||||
Install bb-freeze, then in the root of a Tahoe source tree with full path
|
||||
`<tahoedir>`, on Windows do:
|
||||
```
|
||||
|
@ -294,7 +294,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 <http://www.python.org/getit/releases/2.7.3/> .
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
3. Open a command prompt and cd to the top of the Tahoe-LAFS tree (e.g. `cd \tahoe-lafs`).
|
||||
|
||||
|
@ -313,11 +313,11 @@ Note that this assumes that you install Python in the default location (C:\Pytho
|
|||
|
||||
The 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):
|
||||
|
||||
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++.
|
||||
1. 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++.
|
||||
|
||||
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 [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):
|
||||
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):
|
||||
|
||||
```
|
||||
[build]
|
||||
|
@ -333,7 +333,7 @@ If you receive "error: Setup script exited with error: command 'gcc' failed with
|
|||
<a name="point9.4.2"></a>
|
||||
#### How do I make it run as a Windows service?
|
||||
|
||||
<http://agiletesting.blogspot.com/2005/09/running-python-script-as-windows.html>
|
||||
<https://agiletesting.blogspot.com/2005/09/running-python-script-as-windows.html>
|
||||
|
||||
<a name="point9.4.3"></a>
|
||||
#### How do I make it run under a different user account?
|
||||
|
|
Loading…
Reference in a new issue