2007-02-15 01:11:02 +00:00
|
|
|
Deluge BitTorrent Client
|
|
|
|
|
|
|
|
|
|
Authors:
|
|
|
|
|
Zach Tibbitts, aka zachtib
|
|
|
|
|
Alon Zakai, aka kripkenstein
|
2007-06-10 20:16:42 +00:00
|
|
|
Marcos Pinto, aka markybob
|
2007-02-15 01:11:02 +00:00
|
|
|
|
|
|
|
|
Homepage: http://deluge-torrent.org
|
|
|
|
|
|
|
|
|
|
==========================
|
|
|
|
|
Installation Instructions:
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
First, make sure you have the proper bulid
|
|
|
|
|
dependencies installed. On a normal Debian
|
|
|
|
|
or Ubuntu system, those dependencies are:
|
|
|
|
|
|
2007-06-08 23:02:59 +00:00
|
|
|
g++
|
2007-02-15 01:11:02 +00:00
|
|
|
python-all-dev
|
|
|
|
|
python-all
|
|
|
|
|
python-support
|
|
|
|
|
libboost-dev
|
|
|
|
|
libboost-thread-dev
|
|
|
|
|
libboost-date-time-dev
|
|
|
|
|
libboost-filesystem-dev
|
2007-06-12 19:41:17 +00:00
|
|
|
libboost-serialization-dev
|
2007-06-07 22:30:20 +00:00
|
|
|
libssl-dev
|
2007-02-15 01:11:02 +00:00
|
|
|
zlib1g-dev
|
|
|
|
|
|
|
|
|
|
But the names of the packages may vary
|
|
|
|
|
depending on your OS / distro.
|
|
|
|
|
|
|
|
|
|
Once you have the needed libraries installed,
|
|
|
|
|
build Deluge by running:
|
|
|
|
|
|
|
|
|
|
python setup.py build
|
|
|
|
|
|
|
|
|
|
You shouldn't get any errors. Then run, as
|
|
|
|
|
root (or by using sudo):
|
|
|
|
|
|
|
|
|
|
python setup.py install
|
|
|
|
|
|
|
|
|
|
and Deluge will be installed.
|
|
|
|
|
|
|
|
|
|
You can then run Deluge by executing:
|
|
|
|
|
|
|
|
|
|
deluge
|
|
|
|
|
|
|
|
|
|
Notes:
|
|
|
|
|
|
|
|
|
|
1) On some distributions, boost libraries are
|
|
|
|
|
renamed to have "-mt" at the end (boost_thread_mt
|
|
|
|
|
instead of boost_thread, for example), the "mt"
|
|
|
|
|
indicating "multithreaded". In some cases it
|
|
|
|
|
appears the distros lack symlinks to connect
|
|
|
|
|
things. The solution is to either add symlinks
|
|
|
|
|
from the short names to those with "-mt", or to
|
|
|
|
|
alter setup.py to look for the "-mt" versions.
|
2007-06-11 20:12:33 +00:00
|
|
|
|
|
|
|
|
2) After upgrading your Deluge installation, it
|
|
|
|
|
may fail to start. If this happens to you, you
|
|
|
|
|
need to remove your ~/.config/deluge directory
|
|
|
|
|
to allow Deluge to rebuild it's configuration
|
|
|
|
|
file.
|
