Deluge Forum

http://dev.deluge-torrent.org/wiki/User ... pt/FreeBSD
Deluged

and use csh shell change this
/dev/null 2>&1
to
&/dev/null

FreeBSD port of Deluge 1.3.1 marked as "broken".
http://www.freshports.org/net-p2p/deluge/

Fix this, please.

Welcome to dependency hell.

It's exactly what the ports collection was designed to avoid.

atealus wrote:FreeBSD port of Deluge 1.3.1 marked as "broken".
http://www.freshports.org/net-p2p/deluge/

Fix this, please.

The Deluge developers supply the source code but it is up to to other volunteers to package it. So you would need to speak to the freshports maintainer.

Is Deluge still completely unmaintainable in FreeBSD?

I notice the port has been removed from the collection due to dependency breakage ... five months ago. Is anyone here maintaining it?

I'm tempted to give Deluge another go, having switched to something else a year back or more. Is there a headless option in Makefile/configure.py yet?

Well, the good news is that after many hours of battling with various dependencies I've managed to get deluge1.32 to install and deluged to run in FreeBSD8.1.

The other good news is that deluge1.31 gtk gui connects to the remote daemon just fine from my Natty desktop.

Three cheers for me.

Good to hear you got it installed and working on FreeBSD.

Would be helpful if you could update the install guide or just post the steps you took.

I could do that ... but as it took over 12 hours to achieve I'm not sure it's the best advert

First thing I did was go to the freshports page and install everything listed in the depends from ports. That's what took all the time. Some of them are a real BITCA to get installed, and for the things that just won't compile at all you have to use pkg_add -r - and that *will* break anything else you have that uses perl or python. My end philosophy was to hell with it all, let everything break and at the end delete the older versions of perl and python that have been dragged in and 'pkgdb -fF' then 'portupgrade -fr perl-threaded-5* python26*' which will take an age, but will fix everything back to working.

I think the best tip is to make sure you don't have WITHOUT_X11 in /etc/make.conf - cairo is the only thing that checks for it and disables cairo_xlib if it finds it. You have no idea how much thrashing around that one caused until I finally got it nailed. Then I could compile gtk20 and py26_gtk20.

Once all the depends are satisfied it's a simple breeze to follow the given instructions in the README to use setup.py build/install.

py-game still won't compile, but it doesn't seem to matter to anyone.

Of course, this would have been a lot easier if the ports maintainer just maintained the port. Preferably breaking deluge into its component parts: deluged (daemon), delugew (webui), delugec (console) and deluge (gtk) like transmission is. I'd say that about 95% of my fight was for irrelevant stuff in a headless environment, and it'd be nice to not have to do it.

I'm happy I got it working though. I can remove the dummynet packet-shaping from my ipfw2 firewall now, as deluge has always played nice with bandwidth limits including IP overhead.

Good to be back.