I want install 'deluge'. There is no *.tgz in the linuxpackages.net or
other web sites, so I'm about to install it from source.
I read the README, it needs these dependencies:
g++
make
python-all-dev
python-all version >= 2.4
python-dbus
python-gnome2-extras
python-gtk2 version >= 2.9
python-notify
python-pyopenssl
librsvg2-common
python-xdg
python-support
libboost-dev >= 1.33.1
libboost-thread-dev
libboost-date-time-dev
libboost-filesystem-dev
libboost-serialization-dev
libssl-dev
zlib1g-dev
I search the packages in the KPackage, I found that there were only :
################
python-2.5.1-i486-1
dbus-1.0.2
dbus-glib-0.73
dbus-qt3-0.70
librsvg-2.16.1-1486-1
boost-1.34.1-i486-1gds(It doesn't exist in original slk12, I installed
one boost*.tgz package)
openssl-0.9.8e
openssl-solibs-0.9..8e
zlib-1.2.3-i486-2
#################
'Deluge' needs so many python*(like python-all, etc). I have
python-2.5.1, which python-* packages above I need to install ?
And what the librsvg2-common is ? I need it ?
What the libboost-* packages are? After installing the boost-1.34.1-
i486-1gds.tgz, does that mean I have met the libboost-* dependencies ?
And how about libssl-dev & zlib1g-dev ?
I have never seen so many dependencies software requires before. Does
'Deluge' deserve installation ?
Search the packages with less and see what's there. If something
you need isn't there, then you'll have to get it elsewhere.
(see below)
>
> And what the librsvg2-common is ? I need it ?
That's what the README says.
(see below)
>
> What the libboost-* packages are? After installing the boost-1.34.1-
> i486-1gds.tgz, does that mean I have met the libboost-* dependencies ?
Try:
ldd `which boost` # for example
Or do:
locate libboost
(don't forget to do: updatedb so that your locate database is up-to-date)
If you don't find the lib that way, then you need to install it seperately.
>
> And how about libssl-dev & zlib1g-dev ?
That's what it says....
Debian has a staggering number of source and binary packages available. Check
debian.org. Redhat too. And there are tools for converting debs
and rpms into slackpackages.
You can always try to build the package, and if it fails, check out
the error messages to find out what it really needs.
Then just delete the source directory and un-tar-gzip the tarball
again and try to build it again when you've made a good stab at
fulfilling the dependencies. I've sometimes had to do this a
dozen times to get it right. Those READMEs are sometimes really
inadequate, although this one looks pretty thorough.
>
> I have never seen so many dependencies software requires before. Does
> 'Deluge' deserve installation ?
I have no idea what Deluge is. Sounds like you might need a rowboat
to go with it :-)
But I'm not the one to ask about that. I don't think KDE deserves
installation.
Tom
--
simpleman.s43
That would be at gee male
> I have never seen so many dependencies software requires before. Does
> 'Deluge' deserve installation ?
Install PyGTK and pyOpenSSL and then give it a try, I think thats all
you need.
The list of dependencies looks like something from a RPM based system,
here most packages are split in twos (or more) like zlib and
zlib-dev. zlib meets other programs dependencies and zlib-dev is only
needed if you want to compile programs against zlib.
--
Thomas O.
This area is designed to become quite warm during normal operation.
> I want install 'deluge'. There is no *.tgz in the linuxpackages.net or
> other web sites, so I'm about to install it from source.
Before you go doing that have you tried Ktorrent first? Because Ktorrent is
KDE native.
> I have never seen so many dependencies software requires before. Does
> 'Deluge' deserve installation ?
Only if you feel that other alternative Torrent programs do not offer what
deluge does.
Richard James
> vvoody wrote :
>
>> I have never seen so many dependencies software requires before. Does
>> 'Deluge' deserve installation ?
>
> Install PyGTK and pyOpenSSL and then give it a try, I think thats all
> you need.
>
> The list of dependencies looks like something from a RPM based system,
> here most packages are split in twos (or more) like zlib and zlib-dev.
> zlib meets other programs dependencies and zlib-dev is only needed if
> you want to compile programs against zlib.
exactly : package like python-dev, coincoin-lib, bullshit-dev, ... are
only found on rpm and deb based distribution. On source one, there only 1
package for -lib, -dev, -core.
For instance, I have python-2.5.1 installed, does that mean I have the
python-all, python-all-dev ?
After solving the dependencies and compiling the deluge, I run the
deluge. But:
vvoody@vvhostname:/usr/local/deluge-0.5.8/bin$ ./deluge
Traceback (most recent call last):
File "./deluge", line 42, in <module>
import deluge
ImportError: No module named deluge
###################################
pygobject-2.14.0
cairo-1.4.12(update from 1.4.10)
pycairo-1.4.12
pygtk-2.12.0
I installed them successfully, so is the deluge-0.5.8. What does the
error mean? I don't know Python.
Is that what all the fuss is about? A bittorrent client?
I use ctorrent and it compiled in about 5 seconds and works
perfectly. It is very fast.
ldd `which ctorrent`
linux-gate.so.1 => (0xffffe000)
libssl.so.0 => /usr/lib/libssl.so.0 (0xb7f99000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7eb5000)
libm.so.6 => /lib/libm.so.6 (0xb7e8e000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7e83000)
libc.so.6 => /lib/libc.so.6 (0xb7d41000)
libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0xb7c03000)
libdl.so.2 => /lib/libdl.so.2 (0xb7bfe000)
/lib/ld-linux.so.2 (0xb7fe2000)
Yes, it's a GUI bittorrent client based on PyGtk.
Command line BT client? Maybe I'll try that.
> I installed them successfully, so is the deluge-0.5.8. What does the
> error mean? I don't know Python.
Maybe you should try the Deluge forum:
<URL: http://forum.deluge-torrent.org/viewforum.php?f=7>
Thanks. I have posted the problem.
I installed the deluge*.tgz which is from slacky.it, but the same
error appeared.
$sudo installpkg -root ~/d/ deluge-0.5.7.1-i486-1as.tgz
vvoody@vvhostname:~/d/usr/bin$ ./deluge
> I installed the deluge*.tgz which is from slacky.it, but the same
> error appeared.
> $sudo installpkg -root ~/d/ deluge-0.5.7.1-i486-1as.tgz
> vvoody@vvhostname:~/d/usr/bin$ ./deluge
> Traceback (most recent call last):
> File "./deluge", line 42, in <module>
> import deluge
> ImportError: No module named deluge
Unless you know what you are doing in Slackware (which I think will
take you some more time) I would *never* add "-root ~/d/" to the
installpkg command.
If you do so, you will have to add extra directories to all sorts of
environment variables (PATH, MANPATH for instance) and go through all
kinds of hoops to make other programs find your installed package. THe
above errors originate from the fact that python cannot find the
package content you just installed into a non-default location.
Eric
Possibility 1
They have named their module the same as their program
try calling that program outside of the directory
/$ /usr/local/deluge-0.5.8/bin/deluge
Possibility 2
The deluge module is not installed into the PYTHON_PATH
Run python interactively
$ python
from the >>> prompt type in the following lines
import sys
sys.path
what it prints out is the path that python searches for modules in. When you
built and installed the deluge program it should have put the deluge module
in one of those locations. The deluge module would be named deluge.py or
deluge.pyc
to see if the module is in the current path type
import deluge
if python comes back with the >>> prompt then it is in the path if it errors
like
>>> import deluge
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named deluge
Then it is not in pythons path
then press ctrl-d to quit python
Richard James
> Possibility 2
> The deluge module is not installed into the PYTHON_PATH
> Run python interactively
> $ python
> from the >>> prompt type in the following lines
> import sys
> sys.path
> what it prints out is the path that python searches for modules in. When you
> built and installed the deluge program it should have put the deluge module
> in one of those locations. The deluge module would be named deluge.py or
> deluge.pyc
> to see if the module is in the current path type
>>> sys.path
['', '/usr/lib/python25.zip', '/usr/lib/python2.5', '/usr/lib/
python2.5/plat-linux2', '/usr/lib/python2.5/lib-tk', '/usr/lib/
python2.5/lib-dynload', '/usr/lib/python2.5/site-packages']
I removed the /usr/local/deluge-0.5.8/. Then I used the prefix=/usr/
local/ to reinstall the deluge. After that, 'deluge' directory
appeared in the /usr/local/lib/python2.5/site-packages/. BUT there is
no 'deluge.py' or 'deluge.pyc' in it.
I know I should use prefix=/usr because python doesn't search the /usr/
local/lib/python2.5/site-pachages. I'll try that later. Even though I
change the prefix, there still will not be a 'deluge.py' or
'deluge.pyc'. Why I cannt get a 'deluge.py' ?
> import deluge
> if python comes back with the >>> prompt then it is in the path if it errors
> like>>> import deluge
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ImportError: No module named deluge
> Then it is not in pythons path
> then press ctrl-d to quit python
>
Yes, no module.
I have buildscripts for deluge and all of its deps and here is what i
had to install on bluewhite64 12.0 (which looks like being
"compatible" to Slackware 12.0 except it is x86_64):
boost-1.34.1-x86_64-1slp
dbus-python-0.82.4-x86_64-1slp
pygobject-2.14.0-x86_64-1slp
pycairo-1.4.0-x86_64-1slp
pygtk-2.12.0-x86_64-1slp
pyxdg-0.15-x86_64-1slp
deluge-0.5.7.1-x86_64-1slp
I compiled all packages from source and it seem to work. Anyway: For
KDE i recommend using ktorrent as already mentioned on this thread.
deluge is using way tooo many external libraries.
If you are interested in the build scripts... email me... or ask
google.
Markus
P.S. I'm using bittorando from the command line and that works also...
Thank you. After installing the pyxdg and dbus-python, deluge
*works*.
Many thanks to everyone above:-)
Markus
Way to go!
> For instance, I have python-2.5.1 installed, does that mean I have the
> python-all, python-all-dev ?
Yes. Unlike most other distributions, Slackware packages tend to be
complete and put the whole shebang, including development files,
libraries, etc. in a single package. This is less fine-grained but
easier to use.
- Martijn
Where can I see the information of the packages whether they include
development , libraries files or not ?
> Where can I see the information of the packages whether they include
> development , libraries files or not ?
You can see the complete contents of the packages (except symlinks) in
the files in the /var/log/packages directory.
- Martijn