2012-05-10 10:26:39 +02:00
|
|
|
# Common
|
2005-08-18 20:41:26 +02:00
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
First things first: Supybot *requires* at least Python 2.6. There
|
2012-05-10 10:26:39 +02:00
|
|
|
isn't any way to get around it. You can get it from [Python homepage].
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
[Python homepage]:http://python.org/
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
# Recommended Software
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2014-03-04 14:51:16 +01:00
|
|
|
The following libraries are not needed for running Limnoria, but enable
|
|
|
|
extra features you may want. (Order by decreasing estimated usefulness)
|
|
|
|
|
|
|
|
[charade] -- enables better encoding handling
|
|
|
|
|
|
|
|
[pytz] and [python-dateutil] -- enable additional features of the `Time` plugin
|
|
|
|
|
|
|
|
[python-gnupg] -- enables user authentication with GPG
|
|
|
|
|
|
|
|
[charade]:https://pypi.python.org/pypi/charade
|
|
|
|
[pytz]:https://pypi.python.org/pypi/pytz
|
|
|
|
[python-dateutil]:https://pypi.python.org/pypi/python-dateutil
|
2014-03-04 14:55:05 +01:00
|
|
|
[python-gnupg]:https://pypi.python.org/pypi/python-gnupg
|
2012-05-10 10:26:39 +02:00
|
|
|
|
2014-04-30 18:57:51 +02:00
|
|
|
To install them, run
|
|
|
|
|
|
|
|
```pip install -r requirements.txt```
|
|
|
|
|
|
|
|
or if you don't have or want to use root,
|
|
|
|
|
|
|
|
````pip --install-option=--prefix=$HOME/.local install -r requirements.txt```
|
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
For more information and help on how to use Supybot, checkout
|
2012-05-27 11:44:42 +02:00
|
|
|
the documents under [docs/], especially [GETTING_STARTED] and
|
2014-05-20 18:15:41 +02:00
|
|
|
[CONFIGURATION], or on [the website]
|
2012-05-27 11:36:00 +02:00
|
|
|
|
|
|
|
[docs/]:docs/index.rst
|
2014-05-20 18:15:41 +02:00
|
|
|
[GETTING_STARTED]:docs/GETTING_STARTED.rst
|
|
|
|
[CONFIGURATION]:docs/CONFIGURATION.rst
|
|
|
|
[the website]:http://supybot.aperio.fr/doc/use/index.html
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
So what do you do? That depends on which operating system you're
|
2005-08-18 20:41:26 +02:00
|
|
|
running. We've split this document up to address the different
|
|
|
|
methods, so find the section for your operating system and continue
|
|
|
|
from there.
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
# UNIX/Linux/BSD
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
If you're installing Python using your distributor's packages, you may
|
2014-02-21 16:38:40 +01:00
|
|
|
need a python-dev or python3-dev package installed, too. If you don't have
|
|
|
|
a '/usr/lib/python2.x/distutils' directory or
|
|
|
|
'/usr/lib/python2.x/config/Makefile' or with Python 3
|
|
|
|
'/usr/lib/python3.x/distutils' or '/usr/lib/python3.x/config/Makefile' (assuming '/usr/lib/python2.x' or '/usr/lib/python3.x' is where your Python
|
|
|
|
libs are installed), then you will need a python-dev or python3-dev package.
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
First start by git cloning Limnoria and moving to the cloned repository.
|
|
|
|
|
|
|
|
```
|
|
|
|
git clone git://github.com/ProgVal/Limnoria.git
|
|
|
|
cd Limnoria
|
|
|
|
```
|
|
|
|
|
|
|
|
The rest depends on do you have root access and do you want to perform global or local install.
|
|
|
|
|
|
|
|
## Global install
|
|
|
|
|
|
|
|
Run
|
|
|
|
|
|
|
|
```
|
|
|
|
python setup.py install
|
|
|
|
```
|
|
|
|
|
2014-02-21 16:38:40 +01:00
|
|
|
```python``` can be replaced with ```python2``` (if your distribution
|
|
|
|
uses Python 3 by default) or ```python3``` if you want to use Python 3
|
|
|
|
version.
|
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
Now you have several new programs installed where Python scripts are normally
|
2005-08-18 20:41:26 +02:00
|
|
|
installed on your system ('/usr/bin' or '/usr/local/bin' are common on
|
|
|
|
UNIX systems). The two that might be of particular interest to you, the
|
|
|
|
new user, are 'supybot' and 'supybot-wizard'. The former, 'supybot', is
|
|
|
|
the script to run an actual bot; the latter, 'supybot-wizard', is an
|
|
|
|
in-depth wizard that provides a nice user interface for creating a
|
|
|
|
registry file for your bot.
|
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
## Local install
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
Run
|
2005-01-19 14:14:38 +01:00
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
```
|
|
|
|
python setup.py install --user
|
|
|
|
```
|
|
|
|
|
2014-02-21 16:38:40 +01:00
|
|
|
```python``` can be replaced with ```python2``` (if your distribution
|
|
|
|
uses Python 3 by default) or ```python3``` if you want to use
|
|
|
|
Python 3 version.
|
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
and you will have new programs installed in ~/.local/bin. The two that might be of particular interest to you, the
|
|
|
|
new user, are 'supybot' and 'supybot-wizard'. The former, 'supybot', is
|
|
|
|
the script to run an actual bot; the latter, 'supybot-wizard', is an
|
|
|
|
in-depth wizard that provides a nice user interface for creating a
|
|
|
|
registry file for your bot.
|
|
|
|
|
|
|
|
By default you must run the bot with full path to the binary unless you specify $PATH.
|
|
|
|
|
2014-05-01 10:20:45 +02:00
|
|
|
Run the following command to fix your PATH. We presume that you use bash
|
|
|
|
and if you don't, you most probably know how to do this with other shell.
|
2012-05-10 10:26:39 +02:00
|
|
|
|
|
|
|
```
|
2014-05-01 11:17:28 +02:00
|
|
|
echo 'PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
|
2014-05-01 11:12:27 +02:00
|
|
|
source ~/.bashrc
|
2012-05-10 10:26:39 +02:00
|
|
|
```
|
|
|
|
|
2012-05-10 10:51:59 +02:00
|
|
|
# Upgrading
|
|
|
|
|
|
|
|
To upgrade, return to the cloned Limnoria repository and run:
|
|
|
|
|
|
|
|
```
|
|
|
|
git pull
|
|
|
|
```
|
|
|
|
|
|
|
|
and then install Limnoria normally. "python setup.py install" doesn't affect config files of the bot any way.
|
|
|
|
|
|
|
|
If you don't have the cloned Limnoria repository, clone it again using the installation instructions.
|
|
|
|
|
2014-02-21 16:38:40 +01:00
|
|
|
## Upgrading to Python 3
|
|
|
|
|
|
|
|
Upgrading Python3 happens the same way, but if you want to move from 2 to 3
|
2014-02-21 17:24:38 +01:00
|
|
|
or 3 to 2, you must remove the build/ directory and the executable
|
|
|
|
supybot* files first. The build/ directory is on same directory as this
|
|
|
|
file and supybot* are usually in /usr/local/bin or ~/.local/bin
|
2014-02-21 16:38:40 +01:00
|
|
|
|
|
|
|
```
|
|
|
|
rm -rf build/
|
2014-02-21 17:24:38 +01:00
|
|
|
rm /usr/local/bin/supybot*
|
|
|
|
rm ~/.local/bin/supybot*
|
2014-02-21 16:38:40 +01:00
|
|
|
```
|
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
# Windows
|
2005-08-18 20:41:26 +02:00
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
**Note**: If you are using an IPV6 connection, you will not be able
|
2005-08-18 20:41:26 +02:00
|
|
|
to run Supybot under Windows (unless Python has fixed things). Current
|
2005-01-19 14:14:38 +01:00
|
|
|
versions of Python for Windows are *not* built with IPV6 support. This
|
|
|
|
isn't expected to be fixed until Python 2.4, at the earliest.
|
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
Now that you have Python installed, open up a command prompt. The
|
2005-01-19 14:14:38 +01:00
|
|
|
easiest way to do this is to open the run dialog (Programs -> run) and
|
2005-08-18 20:41:26 +02:00
|
|
|
type "cmd" (for Windows 2000/XP/2003) or "command" (for Windows 9x). In
|
|
|
|
order to reduce the amount of typing you need to do, I suggest adding
|
|
|
|
Python's directory to your path. If you installed Python using the
|
|
|
|
default settings, you would then do the following in the command prompt
|
|
|
|
(otherwise change the path to match your settings)::
|
|
|
|
|
2012-05-10 10:26:39 +02:00
|
|
|
```
|
|
|
|
set PATH=C:\Python2x\;%PATH%
|
|
|
|
```
|
2005-08-18 20:41:26 +02:00
|
|
|
|
2012-05-10 10:30:00 +02:00
|
|
|
You should now be able to type 'python' to start the Python
|
2005-08-18 20:41:26 +02:00
|
|
|
interpreter. Exit by pressing CTRL-Z and then Return. Now that that's
|
|
|
|
setup, you'll want to cd into the directory that was created when you
|
|
|
|
unzipped Supybot; I'll assume you unzipped it to 'C:\Supybot' for these
|
2012-05-10 10:26:39 +02:00
|
|
|
instructions. From 'C:\Supybot', run
|
|
|
|
|
|
|
|
```
|
|
|
|
python setup.py install
|
|
|
|
```
|
|
|
|
|
|
|
|
This will install Supybot under 'C:\Python2x\'. You will now have several new
|
2009-05-18 06:18:02 +02:00
|
|
|
programs installed in 'C:\Python2x\Scripts\'. The two that might be of
|
2005-08-18 20:49:12 +02:00
|
|
|
particular interest to you, the new user, are 'supybot' and 'supybot-wizard'.
|
|
|
|
The former, 'supybot', is the script to run an actual bot; the latter,
|
|
|
|
'supybot-wizard', is an in-depth wizard that provides a nice user interface for
|
|
|
|
creating a registry file for your bot.
|