19 | | There are a few 3rd party libraries that Tahoe-LAFS depends on that |
20 | | might not be easy to set up on your platform. If the following |
21 | | instructions don't Just Work without any further effort on your part, |
22 | | then please write to `the tahoe-dev mailing list |
23 | | <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`_ where |
24 | | friendly hackers will help you out. |
| 20 | There are a few 3rd party libraries that Tahoe-LAFS depends on that might not |
| 21 | be easy to set up on your platform. If the following instructions don't Just |
| 22 | Work without any further effort on your part, then please write to `the |
| 23 | tahoe-dev mailing list |
| 24 | <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`_ where friendly |
| 25 | hackers will help you out. |
29 | | Check if you already have an adequate version of Python installed by |
30 | | running ``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5, |
31 | | Python v2.6, or Python v2.7 will work. Python v3 does not work. On |
32 | | Windows, we recommend the use of Python v2.6 (native, not Cygwin). If |
33 | | you don't have one of these versions of Python installed, then follow |
34 | | the instructions on `the Python download page |
35 | | <http://www.python.org/download/releases/2.6.6/>`_ to download and |
36 | | install Python v2.6. Make sure that the path to the installation |
37 | | directory has no spaces in it (e.g. on Windows, do not install Python |
38 | | in the "Program Files" directory). |
| 30 | Check if you already have an adequate version of Python installed by running |
| 31 | ``python -V``. Python v2.4 (v2.4.4 or greater), Python v2.5, Python v2.6, or |
| 32 | Python v2.7 will work. Python v3 does not work. On Windows, we recommend the |
| 33 | use of native Python, not Cygwin. If you don't have one of these versions of |
| 34 | Python installed, then follow the instructions on `the Python download page |
| 35 | <http://www.python.org/download/releases/2.7.2/>`_ to download and install |
| 36 | Python v2.7. Make sure that the path to the installation directory has no |
| 37 | spaces in it (e.g. on Windows, do not install Python in the "Program Files" |
| 38 | directory). |
55 | | On Windows, the ``build`` step might tell you to open a new Command |
56 | | Prompt (or, on XP and earlier, to log out and back in again). This is |
57 | | needed the first time you set up Tahoe-LAFS on a particular |
58 | | installation of Windows. |
| 55 | On Windows, the ``build`` step might tell you to open a new Command Prompt |
| 56 | (or, on XP and earlier, to log out and back in again). This is needed the |
| 57 | first time you set up Tahoe-LAFS on a particular installation of Windows. |
70 | | executable in the ``bin`` directory can configure and launch your |
71 | | Tahoe-LAFS nodes. See `running.rst <running.rst>`_ for instructions on |
72 | | how to do that. |
73 | | |
74 | | Advanced Installation |
75 | | --------------------- |
76 | | |
77 | | For optional features such as tighter integration with your operating |
78 | | system's package manager, you can see the `AdvancedInstall |
79 | | <https://tahoe-lafs.org/trac/tahoe-lafs/wiki/AdvancedInstall>`_ wiki page. |
80 | | The options on that page are not necessary to use Tahoe-LAFS and can be |
81 | | complicated, so we do not recommend following that page unless you have |
82 | | unusual requirements for advanced optional features. For most people, |
83 | | you should first follow the instructions on this page, and if that |
84 | | doesn't work then ask for help by writing to `the tahoe-dev mailing |
85 | | list <https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>`_. |
86 | | |
| 69 | executable in the ``bin`` directory can configure and launch your Tahoe-LAFS |
| 70 | nodes. See `running.rst <running.rst>`_ for instructions on how to do that. |