I know there was a previous bug on this: (bug #25308 ). However, Heinrich Wendel is wrong. This FAQ http://forum.overnet.com/viewtopic.php?t=52565 is for Windows. There are no hybrid clients for Linux: http://forum.overnet.com/viewtopic.php?t=53556&highlight=hybrid+linux Therefore, I think the addition of the official edonkey command line client to portage would be welcome. The ebuild is based on the overnet one already in portage. I also noticed some errors in the overnet ebuild: 1) IUSE="" is mentioned twice 2) Since this is a binary package shouldn't it go in /opt/bin ?? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 30834 [details] donkey-0.51.2.ebuild
0.53.3 is available on the site. Also, why not just reopen bug #25308? And yes, it is binary and probably should go into /opt- I'll look into that too.
Please correct me if I'm wrong, but I was under the impression that, unless I'm the reporter of that bug or a gentoo dev, I can't reopen that bug. In the past, I tried reopening a few bugs, witout success however (note that they were assigned to gentoo devs so that may have ben why). Regarding the 0.53.3 version (there's also a new 0.53.3 version of overnet out), that wasn't available at the time I submitted the ebuild, but I think the ebuild can work with the new verion without problems. Also please note that the 0.51.2 edonkey version is, supposedly, unstable so it may actually be better if you only add the 0.53.3 version to portage: http://ed2k-gtk-gui.sourceforge.net/core.shtml .... no word on the 0.53.3 version yet since it just came out
I'd like to wait a little while before I commit the overnet/donkey updates to portage- the guis that I've seen for them don't like the way the config files were changed to your home directory. If I commit the overnet/donkey ebuilds, I'll definitely get bugs reported saying things like, "ed2k-gtk-gui can't create the right config files!" Are there guis that work correctly with the newer version of overnet/donkey, or do you think we should wait for guis to support it properly?
I think the problem lies with the cores and not with the GUI (at lest not with ed2k-gtk-gui). I'm running an overnet->ed2k-gtk-gui setup wothout problems. The problem with the cores is that they save their config files in the current dir and not in the home directory. I have created an ~/.overnet directory to hold my config filess and when I want to start overnet I "cd ~/.overnet", "overnet -g" and then I run "ed2k_gui". There's a 0.52pre1 version of overnet out (it's not official though) that saves it's config files in ~/.overnet and not the current directory. Versions up to v0.51.2 had this problem. I don't know about v0.53.3. I will investigate and get back to you.
I've tested the 0.53.3 overnet version and it saves it's config files in ~/.overnet by default. Also, you were right about the GUI; like the previous core versions it tries to save the config file in the current directory so, unless you run the core from the ~/.overnet directory, you will have problems. This totally defeats the new overnet feature of saving the config files in ~/.overnet I suppose we should wait a little bit, and hopefully they will release an updated version.
I went ahead and committed the ebuild MASKED into portage. Until frontend support exists for the newer overnet and donkey cores, it will have to remain masked. For when it does come out, I would like to propose a virtual/edonkey or virtual/overnet or something like that. I don't know which is best to use. Any suggestions?
