diff options
25 files changed, 589 insertions, 0 deletions
diff --git a/net-p2p/linux-edonkey-core/Makefile b/net-p2p/linux-edonkey-core/Makefile new file mode 100644 index 000000000000..550c7564338c --- /dev/null +++ b/net-p2p/linux-edonkey-core/Makefile @@ -0,0 +1,57 @@ +# New ports collection makefile for: eDonkey2000 'core' command line client +# Date created: Fri Jan 4 22:44:56 BRST 2002 +# Whom: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> +# +# $FreeBSD$ +# + +PORTNAME= edonkey +PORTVERSION= 0.2000.15.16.58.0.2 +CATEGORIES= net linux +MASTER_SITES= http://users.aber.ac.uk/tpm01/ +PKGNAMESUFFIX= -core +DISTNAME= donkey_s_58test-2 +EXTRACT_SUFX= .gz +EXTRACT_ONLY= + +MAINTAINER= lioux@FreeBSD.org + +ONLY_FOR_ARCHS= i386 +USE_LINUX= yes +NO_WRKSUBDIR= yes +NO_BUILD= yes +STRIP= + +STRIP_CMD= ${LINUXBASE}/usr/bin/strip + +.if exists(/usr/bin/brandelf) +BRANDELF?= /usr/bin/brandelf +.else +BRANDELF?= brandelf +.endif + +BINARY_NAME= donkey + +post-extract: + @${GZCAT} ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX} > ${WRKSRC}/${BINARY_NAME} + +post-patch: + @${SED} -e "s|%%PREFIX%%|${PREFIX}|" ${FILESDIR}/wrapper.sh > \ + ${WRKDIR}/wrapper.sh + +pre-install: +.if exists(${STRIP_CMD}) + @${STRIP_CMD} ${WRKSRC}/${BINARY_NAME} +.endif + @${BRANDELF} -t Linux ${WRKSRC}/${BINARY_NAME} + +do-install: + @${INSTALL_PROGRAM} ${WRKSRC}/${BINARY_NAME} ${PREFIX}/bin/${BINARY_NAME}-real + @${INSTALL_SCRIPT} ${WRKDIR}/wrapper.sh ${PREFIX}/bin/${BINARY_NAME} +.ifndef(NOPORTDOCS) + @${MKDIR} ${DOCSDIR}${PKGNAMESUFFIX} + @${INSTALL_DATA} ${FILESDIR}/README.FreeBSD ${DOCSDIR}${PKGNAMESUFFIX} +.endif + @${SED} s!/usr/local/share/doc/edonkey-core!${DOCSDIR}${PKGNAMESUFFIX}! ${PKGMESSAGE} + +.include <bsd.port.mk> diff --git a/net-p2p/linux-edonkey-core/distinfo b/net-p2p/linux-edonkey-core/distinfo new file mode 100644 index 000000000000..28c7fc8af2b7 --- /dev/null +++ b/net-p2p/linux-edonkey-core/distinfo @@ -0,0 +1 @@ +MD5 (donkey_s_58test-2.gz) = 072d816662a7d2cb9360861eca3424f9 diff --git a/net-p2p/linux-edonkey-core/files/README.FreeBSD b/net-p2p/linux-edonkey-core/files/README.FreeBSD new file mode 100644 index 000000000000..8e5275788f25 --- /dev/null +++ b/net-p2p/linux-edonkey-core/files/README.FreeBSD @@ -0,0 +1,92 @@ +[ HELP file resumed from FAQ at + http://users.aber.ac.uk/tpm01/ed2k_tools/faq.html ] + + Read the aforementioned FAQ for complete instructions. + + 1) You have to configure the 'core' client and add a password + + Install the "net/edonkey-core" port and type 'donkey' +from the command line and then typing 'pass username password' (and +hitting ENTER). Once you are finished, type 'q' (ENTER) and 'y' +(ENTER) to quit and make the core save its preferences. + + Of course, username must be a username you desire; and, +password, a password you want to use. These are for connecting to +the 'core' client, not for anything else. Therefore, unless you +want someone mischiefly connecting to your client, choose both +carefully. :) + + 2) Start 'core' client prior to running any of the GUIs +after you have setup a password + + To start the core client to make it controllable via a GUI, +type 'donkey - !' from the command line. + + 3) Run the GUI and connect to the core client + + Install the port "net/edonkey-gui-gtk" or "net/edonkey-gui-java", +whichever one you prefer. Next run 'ed2k_gui' (if you chose the GTK +gui client) or 'edonkey2000-gui-java' (if you chose the Java gui +client). The Java GUI still lacks many features but it can modify +configuration parameters whereas the GTK has many features but +cannot modify anything. Therefore, I would advise using both, each +for what it is strong. The java one to configure and the GTK one +for normal use. + + Okay, the GUI starts and there is that 'connect to' dialog, +now what do I do? + + First of all, you'll need an edonkey core running somewhere. +Usually this will be the computer you're running the GUI on. There +should be a status message above the buttons that tell you if there +is already a core running locally or not. If not, hit the 'spawn +local donkey' button to start the edonkey2000 core program. Now the +status message should change. If not, you'll have to start the core +client manually (Refer to step #2). + + Second, if you spawned the donkey core alright, you enter +the admin username and password into the appropriate fields in the +'connect to' dialog and hit the 'connect' button. Now the 'connect +to' dialog should disappear and the GUI should be connected to the +core. If this does not happen, there could be the following problems +(also check the statusbar of the GUI main window for messages): + + (a) If you have started the core manually, you forgot the '-' + option. Start it with 'donkey - !' from the command line. + + (b) You're connecting to the wrong computer ('host'). This should + be 'localhost' by default. + + (c) You're connecting to the wrong port on your computer. The + default GUI port can be set in the command line 'core' client via + the 'aport' command, but should be 4663 by default. + + (d) You haven't set a username and/or password with the core + manually (Refer to step #1). + + (e) Your username/password are wrong (run the core manually and + type the 'vo' command to see what they are set to). + + (f) The 'connect to' dialog disappears, but nothing seems to + happen. Most notably, the options page shows 'pleasewait' as a + nickname: This happens if you connect to the core on the wrong + port, namely on the port the core uses as its _data_ port. Start + the core manually and type 'vo' to see what the admin port is. + Make sure the 'admin port' is different from the 'door port' + (=data port). If in doubt, type 'netstat -l' from the command + line to see on what ports the donkey is listening. It should be + one of those. + + (g) If you're trying to control a GUI on a remote host, chances + are that there is a firewall between you and the remote host that + blocks all TCP connections on the admin port. If this is the case, + you have to check your firewall settings and allow these connections + or try a different port as an admin port. + + Third, you're connected, and the options page does NOT show +'pleasewait' as a nickname. This is a very good sign, meaning that +the GUI and the core can actually talk to each other. Now you should +be able to do whatever you want: Go to the servers page and connect +to a server first. Then you can search and start to download things. +If you right-click on the list-entries you'll get all the available +actions. Don't forget to share! :) diff --git a/net-p2p/linux-edonkey-core/files/wrapper.sh b/net-p2p/linux-edonkey-core/files/wrapper.sh new file mode 100644 index 000000000000..46fd18de71cd --- /dev/null +++ b/net-p2p/linux-edonkey-core/files/wrapper.sh @@ -0,0 +1,23 @@ +#!/bin/sh + +PREFIX="%%PREFIX%%" +PROGRAM="${0}" +DIRNAME=${HOME}/.edonkey2000-core + +if [ ! -d ${DIRNAME} ] +then + mkdir -p ${DIRNAME} +fi + +if [ ! -h ${DIRNAME}/${PROGRAM##*/} ] +then + ln -sf ${PREFIX}/bin/${PROGRAM##*/}-real ${DIRNAME}/${PROGRAM##*/} +fi + +echo " ${*} " | grep " \-createdironly " || +{ + cd ${DIRNAME} && + echo Running under ${DIRNAME} && + exec ./${PROGRAM##*/} ${*} || + echo PROBLEM. Cannot create directory ${DIRNAME}, make sure you have the proper permissions to create it and try again +} diff --git a/net-p2p/linux-edonkey-core/pkg-comment b/net-p2p/linux-edonkey-core/pkg-comment new file mode 100644 index 000000000000..ee94e3fad6f4 --- /dev/null +++ b/net-p2p/linux-edonkey-core/pkg-comment @@ -0,0 +1 @@ +eDonkey2000 'core' command line client diff --git a/net-p2p/linux-edonkey-core/pkg-descr b/net-p2p/linux-edonkey-core/pkg-descr new file mode 100644 index 000000000000..16c9c6962ea4 --- /dev/null +++ b/net-p2p/linux-edonkey-core/pkg-descr @@ -0,0 +1,10 @@ +The eDonkey2000 'core' is the actual edonkey program which does +everything behind the scenes - connecting to servers, searching, +downloading, uploading, all that stuff. + +The 'core' comes with a very simple text interface (=command line +client), where you can tell it what to do by typing in commands. + +Check http://www.edonkey2000.com/ and the WWW site below. + +WWW: http://users.aber.ac.uk/tpm01/guihome.html diff --git a/net-p2p/linux-edonkey-core/pkg-message b/net-p2p/linux-edonkey-core/pkg-message new file mode 100644 index 000000000000..49bb236a9a3b --- /dev/null +++ b/net-p2p/linux-edonkey-core/pkg-message @@ -0,0 +1,8 @@ + ATTENTIONATTENTION: + +Please make sure that you read +/usr/local/share/doc/edonkey-core/README.FreeBSD. +It contains important information about both configuring and running +edonkey2000 under FreeBSD. You will have problems running it if you +do not read it. + diff --git a/net-p2p/linux-edonkey-core/pkg-plist b/net-p2p/linux-edonkey-core/pkg-plist new file mode 100644 index 000000000000..3f5b8784978a --- /dev/null +++ b/net-p2p/linux-edonkey-core/pkg-plist @@ -0,0 +1,4 @@ +bin/donkey +bin/donkey-real +%%PORTDOCS%%share/doc/edonkey-core/README.FreeBSD +%%PORTDOCS%%@dirrm share/doc/edonkey-core diff --git a/net/Makefile b/net/Makefile index 5a5c6766a4b0..49aaa93f94bd 100644 --- a/net/Makefile +++ b/net/Makefile @@ -92,6 +92,7 @@ SUBDIR += domtools SUBDIR += easysoap SUBDIR += echoping + SUBDIR += edonkey-core SUBDIR += ehnt SUBDIR += etherape SUBDIR += etherboot diff --git a/net/edonkey-core/Makefile b/net/edonkey-core/Makefile new file mode 100644 index 000000000000..550c7564338c --- /dev/null +++ b/net/edonkey-core/Makefile @@ -0,0 +1,57 @@ +# New ports collection makefile for: eDonkey2000 'core' command line client +# Date created: Fri Jan 4 22:44:56 BRST 2002 +# Whom: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> +# +# $FreeBSD$ +# + +PORTNAME= edonkey +PORTVERSION= 0.2000.15.16.58.0.2 +CATEGORIES= net linux +MASTER_SITES= http://users.aber.ac.uk/tpm01/ +PKGNAMESUFFIX= -core +DISTNAME= donkey_s_58test-2 +EXTRACT_SUFX= .gz +EXTRACT_ONLY= + +MAINTAINER= lioux@FreeBSD.org + +ONLY_FOR_ARCHS= i386 +USE_LINUX= yes +NO_WRKSUBDIR= yes +NO_BUILD= yes +STRIP= + +STRIP_CMD= ${LINUXBASE}/usr/bin/strip + +.if exists(/usr/bin/brandelf) +BRANDELF?= /usr/bin/brandelf +.else +BRANDELF?= brandelf +.endif + +BINARY_NAME= donkey + +post-extract: + @${GZCAT} ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX} > ${WRKSRC}/${BINARY_NAME} + +post-patch: + @${SED} -e "s|%%PREFIX%%|${PREFIX}|" ${FILESDIR}/wrapper.sh > \ + ${WRKDIR}/wrapper.sh + +pre-install: +.if exists(${STRIP_CMD}) + @${STRIP_CMD} ${WRKSRC}/${BINARY_NAME} +.endif + @${BRANDELF} -t Linux ${WRKSRC}/${BINARY_NAME} + +do-install: + @${INSTALL_PROGRAM} ${WRKSRC}/${BINARY_NAME} ${PREFIX}/bin/${BINARY_NAME}-real + @${INSTALL_SCRIPT} ${WRKDIR}/wrapper.sh ${PREFIX}/bin/${BINARY_NAME} +.ifndef(NOPORTDOCS) + @${MKDIR} ${DOCSDIR}${PKGNAMESUFFIX} + @${INSTALL_DATA} ${FILESDIR}/README.FreeBSD ${DOCSDIR}${PKGNAMESUFFIX} +.endif + @${SED} s!/usr/local/share/doc/edonkey-core!${DOCSDIR}${PKGNAMESUFFIX}! ${PKGMESSAGE} + +.include <bsd.port.mk> diff --git a/net/edonkey-core/distinfo b/net/edonkey-core/distinfo new file mode 100644 index 000000000000..28c7fc8af2b7 --- /dev/null +++ b/net/edonkey-core/distinfo @@ -0,0 +1 @@ +MD5 (donkey_s_58test-2.gz) = 072d816662a7d2cb9360861eca3424f9 diff --git a/net/edonkey-core/files/README.FreeBSD b/net/edonkey-core/files/README.FreeBSD new file mode 100644 index 000000000000..8e5275788f25 --- /dev/null +++ b/net/edonkey-core/files/README.FreeBSD @@ -0,0 +1,92 @@ +[ HELP file resumed from FAQ at + http://users.aber.ac.uk/tpm01/ed2k_tools/faq.html ] + + Read the aforementioned FAQ for complete instructions. + + 1) You have to configure the 'core' client and add a password + + Install the "net/edonkey-core" port and type 'donkey' +from the command line and then typing 'pass username password' (and +hitting ENTER). Once you are finished, type 'q' (ENTER) and 'y' +(ENTER) to quit and make the core save its preferences. + + Of course, username must be a username you desire; and, +password, a password you want to use. These are for connecting to +the 'core' client, not for anything else. Therefore, unless you +want someone mischiefly connecting to your client, choose both +carefully. :) + + 2) Start 'core' client prior to running any of the GUIs +after you have setup a password + + To start the core client to make it controllable via a GUI, +type 'donkey - !' from the command line. + + 3) Run the GUI and connect to the core client + + Install the port "net/edonkey-gui-gtk" or "net/edonkey-gui-java", +whichever one you prefer. Next run 'ed2k_gui' (if you chose the GTK +gui client) or 'edonkey2000-gui-java' (if you chose the Java gui +client). The Java GUI still lacks many features but it can modify +configuration parameters whereas the GTK has many features but +cannot modify anything. Therefore, I would advise using both, each +for what it is strong. The java one to configure and the GTK one +for normal use. + + Okay, the GUI starts and there is that 'connect to' dialog, +now what do I do? + + First of all, you'll need an edonkey core running somewhere. +Usually this will be the computer you're running the GUI on. There +should be a status message above the buttons that tell you if there +is already a core running locally or not. If not, hit the 'spawn +local donkey' button to start the edonkey2000 core program. Now the +status message should change. If not, you'll have to start the core +client manually (Refer to step #2). + + Second, if you spawned the donkey core alright, you enter +the admin username and password into the appropriate fields in the +'connect to' dialog and hit the 'connect' button. Now the 'connect +to' dialog should disappear and the GUI should be connected to the +core. If this does not happen, there could be the following problems +(also check the statusbar of the GUI main window for messages): + + (a) If you have started the core manually, you forgot the '-' + option. Start it with 'donkey - !' from the command line. + + (b) You're connecting to the wrong computer ('host'). This should + be 'localhost' by default. + + (c) You're connecting to the wrong port on your computer. The + default GUI port can be set in the command line 'core' client via + the 'aport' command, but should be 4663 by default. + + (d) You haven't set a username and/or password with the core + manually (Refer to step #1). + + (e) Your username/password are wrong (run the core manually and + type the 'vo' command to see what they are set to). + + (f) The 'connect to' dialog disappears, but nothing seems to + happen. Most notably, the options page shows 'pleasewait' as a + nickname: This happens if you connect to the core on the wrong + port, namely on the port the core uses as its _data_ port. Start + the core manually and type 'vo' to see what the admin port is. + Make sure the 'admin port' is different from the 'door port' + (=data port). If in doubt, type 'netstat -l' from the command + line to see on what ports the donkey is listening. It should be + one of those. + + (g) If you're trying to control a GUI on a remote host, chances + are that there is a firewall between you and the remote host that + blocks all TCP connections on the admin port. If this is the case, + you have to check your firewall settings and allow these connections + or try a different port as an admin port. + + Third, you're connected, and the options page does NOT show +'pleasewait' as a nickname. This is a very good sign, meaning that +the GUI and the core can actually talk to each other. Now you should +be able to do whatever you want: Go to the servers page and connect +to a server first. Then you can search and start to download things. +If you right-click on the list-entries you'll get all the available +actions. Don't forget to share! :) diff --git a/net/edonkey-core/files/wrapper.sh b/net/edonkey-core/files/wrapper.sh new file mode 100644 index 000000000000..46fd18de71cd --- /dev/null +++ b/net/edonkey-core/files/wrapper.sh @@ -0,0 +1,23 @@ +#!/bin/sh + +PREFIX="%%PREFIX%%" +PROGRAM="${0}" +DIRNAME=${HOME}/.edonkey2000-core + +if [ ! -d ${DIRNAME} ] +then + mkdir -p ${DIRNAME} +fi + +if [ ! -h ${DIRNAME}/${PROGRAM##*/} ] +then + ln -sf ${PREFIX}/bin/${PROGRAM##*/}-real ${DIRNAME}/${PROGRAM##*/} +fi + +echo " ${*} " | grep " \-createdironly " || +{ + cd ${DIRNAME} && + echo Running under ${DIRNAME} && + exec ./${PROGRAM##*/} ${*} || + echo PROBLEM. Cannot create directory ${DIRNAME}, make sure you have the proper permissions to create it and try again +} diff --git a/net/edonkey-core/pkg-comment b/net/edonkey-core/pkg-comment new file mode 100644 index 000000000000..ee94e3fad6f4 --- /dev/null +++ b/net/edonkey-core/pkg-comment @@ -0,0 +1 @@ +eDonkey2000 'core' command line client diff --git a/net/edonkey-core/pkg-descr b/net/edonkey-core/pkg-descr new file mode 100644 index 000000000000..16c9c6962ea4 --- /dev/null +++ b/net/edonkey-core/pkg-descr @@ -0,0 +1,10 @@ +The eDonkey2000 'core' is the actual edonkey program which does +everything behind the scenes - connecting to servers, searching, +downloading, uploading, all that stuff. + +The 'core' comes with a very simple text interface (=command line +client), where you can tell it what to do by typing in commands. + +Check http://www.edonkey2000.com/ and the WWW site below. + +WWW: http://users.aber.ac.uk/tpm01/guihome.html diff --git a/net/edonkey-core/pkg-message b/net/edonkey-core/pkg-message new file mode 100644 index 000000000000..49bb236a9a3b --- /dev/null +++ b/net/edonkey-core/pkg-message @@ -0,0 +1,8 @@ + ATTENTIONATTENTION: + +Please make sure that you read +/usr/local/share/doc/edonkey-core/README.FreeBSD. +It contains important information about both configuring and running +edonkey2000 under FreeBSD. You will have problems running it if you +do not read it. + diff --git a/net/edonkey-core/pkg-plist b/net/edonkey-core/pkg-plist new file mode 100644 index 000000000000..3f5b8784978a --- /dev/null +++ b/net/edonkey-core/pkg-plist @@ -0,0 +1,4 @@ +bin/donkey +bin/donkey-real +%%PORTDOCS%%share/doc/edonkey-core/README.FreeBSD +%%PORTDOCS%%@dirrm share/doc/edonkey-core diff --git a/net/linux-edonkey-core/Makefile b/net/linux-edonkey-core/Makefile new file mode 100644 index 000000000000..550c7564338c --- /dev/null +++ b/net/linux-edonkey-core/Makefile @@ -0,0 +1,57 @@ +# New ports collection makefile for: eDonkey2000 'core' command line client +# Date created: Fri Jan 4 22:44:56 BRST 2002 +# Whom: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> +# +# $FreeBSD$ +# + +PORTNAME= edonkey +PORTVERSION= 0.2000.15.16.58.0.2 +CATEGORIES= net linux +MASTER_SITES= http://users.aber.ac.uk/tpm01/ +PKGNAMESUFFIX= -core +DISTNAME= donkey_s_58test-2 +EXTRACT_SUFX= .gz +EXTRACT_ONLY= + +MAINTAINER= lioux@FreeBSD.org + +ONLY_FOR_ARCHS= i386 +USE_LINUX= yes +NO_WRKSUBDIR= yes +NO_BUILD= yes +STRIP= + +STRIP_CMD= ${LINUXBASE}/usr/bin/strip + +.if exists(/usr/bin/brandelf) +BRANDELF?= /usr/bin/brandelf +.else +BRANDELF?= brandelf +.endif + +BINARY_NAME= donkey + +post-extract: + @${GZCAT} ${DISTDIR}/${DISTNAME}${EXTRACT_SUFX} > ${WRKSRC}/${BINARY_NAME} + +post-patch: + @${SED} -e "s|%%PREFIX%%|${PREFIX}|" ${FILESDIR}/wrapper.sh > \ + ${WRKDIR}/wrapper.sh + +pre-install: +.if exists(${STRIP_CMD}) + @${STRIP_CMD} ${WRKSRC}/${BINARY_NAME} +.endif + @${BRANDELF} -t Linux ${WRKSRC}/${BINARY_NAME} + +do-install: + @${INSTALL_PROGRAM} ${WRKSRC}/${BINARY_NAME} ${PREFIX}/bin/${BINARY_NAME}-real + @${INSTALL_SCRIPT} ${WRKDIR}/wrapper.sh ${PREFIX}/bin/${BINARY_NAME} +.ifndef(NOPORTDOCS) + @${MKDIR} ${DOCSDIR}${PKGNAMESUFFIX} + @${INSTALL_DATA} ${FILESDIR}/README.FreeBSD ${DOCSDIR}${PKGNAMESUFFIX} +.endif + @${SED} s!/usr/local/share/doc/edonkey-core!${DOCSDIR}${PKGNAMESUFFIX}! ${PKGMESSAGE} + +.include <bsd.port.mk> diff --git a/net/linux-edonkey-core/distinfo b/net/linux-edonkey-core/distinfo new file mode 100644 index 000000000000..28c7fc8af2b7 --- /dev/null +++ b/net/linux-edonkey-core/distinfo @@ -0,0 +1 @@ +MD5 (donkey_s_58test-2.gz) = 072d816662a7d2cb9360861eca3424f9 diff --git a/net/linux-edonkey-core/files/README.FreeBSD b/net/linux-edonkey-core/files/README.FreeBSD new file mode 100644 index 000000000000..8e5275788f25 --- /dev/null +++ b/net/linux-edonkey-core/files/README.FreeBSD @@ -0,0 +1,92 @@ +[ HELP file resumed from FAQ at + http://users.aber.ac.uk/tpm01/ed2k_tools/faq.html ] + + Read the aforementioned FAQ for complete instructions. + + 1) You have to configure the 'core' client and add a password + + Install the "net/edonkey-core" port and type 'donkey' +from the command line and then typing 'pass username password' (and +hitting ENTER). Once you are finished, type 'q' (ENTER) and 'y' +(ENTER) to quit and make the core save its preferences. + + Of course, username must be a username you desire; and, +password, a password you want to use. These are for connecting to +the 'core' client, not for anything else. Therefore, unless you +want someone mischiefly connecting to your client, choose both +carefully. :) + + 2) Start 'core' client prior to running any of the GUIs +after you have setup a password + + To start the core client to make it controllable via a GUI, +type 'donkey - !' from the command line. + + 3) Run the GUI and connect to the core client + + Install the port "net/edonkey-gui-gtk" or "net/edonkey-gui-java", +whichever one you prefer. Next run 'ed2k_gui' (if you chose the GTK +gui client) or 'edonkey2000-gui-java' (if you chose the Java gui +client). The Java GUI still lacks many features but it can modify +configuration parameters whereas the GTK has many features but +cannot modify anything. Therefore, I would advise using both, each +for what it is strong. The java one to configure and the GTK one +for normal use. + + Okay, the GUI starts and there is that 'connect to' dialog, +now what do I do? + + First of all, you'll need an edonkey core running somewhere. +Usually this will be the computer you're running the GUI on. There +should be a status message above the buttons that tell you if there +is already a core running locally or not. If not, hit the 'spawn +local donkey' button to start the edonkey2000 core program. Now the +status message should change. If not, you'll have to start the core +client manually (Refer to step #2). + + Second, if you spawned the donkey core alright, you enter +the admin username and password into the appropriate fields in the +'connect to' dialog and hit the 'connect' button. Now the 'connect +to' dialog should disappear and the GUI should be connected to the +core. If this does not happen, there could be the following problems +(also check the statusbar of the GUI main window for messages): + + (a) If you have started the core manually, you forgot the '-' + option. Start it with 'donkey - !' from the command line. + + (b) You're connecting to the wrong computer ('host'). This should + be 'localhost' by default. + + (c) You're connecting to the wrong port on your computer. The + default GUI port can be set in the command line 'core' client via + the 'aport' command, but should be 4663 by default. + + (d) You haven't set a username and/or password with the core + manually (Refer to step #1). + + (e) Your username/password are wrong (run the core manually and + type the 'vo' command to see what they are set to). + + (f) The 'connect to' dialog disappears, but nothing seems to + happen. Most notably, the options page shows 'pleasewait' as a + nickname: This happens if you connect to the core on the wrong + port, namely on the port the core uses as its _data_ port. Start + the core manually and type 'vo' to see what the admin port is. + Make sure the 'admin port' is different from the 'door port' + (=data port). If in doubt, type 'netstat -l' from the command + line to see on what ports the donkey is listening. It should be + one of those. + + (g) If you're trying to control a GUI on a remote host, chances + are that there is a firewall between you and the remote host that + blocks all TCP connections on the admin port. If this is the case, + you have to check your firewall settings and allow these connections + or try a different port as an admin port. + + Third, you're connected, and the options page does NOT show +'pleasewait' as a nickname. This is a very good sign, meaning that +the GUI and the core can actually talk to each other. Now you should +be able to do whatever you want: Go to the servers page and connect +to a server first. Then you can search and start to download things. +If you right-click on the list-entries you'll get all the available +actions. Don't forget to share! :) diff --git a/net/linux-edonkey-core/files/wrapper.sh b/net/linux-edonkey-core/files/wrapper.sh new file mode 100644 index 000000000000..46fd18de71cd --- /dev/null +++ b/net/linux-edonkey-core/files/wrapper.sh @@ -0,0 +1,23 @@ +#!/bin/sh + +PREFIX="%%PREFIX%%" +PROGRAM="${0}" +DIRNAME=${HOME}/.edonkey2000-core + +if [ ! -d ${DIRNAME} ] +then + mkdir -p ${DIRNAME} +fi + +if [ ! -h ${DIRNAME}/${PROGRAM##*/} ] +then + ln -sf ${PREFIX}/bin/${PROGRAM##*/}-real ${DIRNAME}/${PROGRAM##*/} +fi + +echo " ${*} " | grep " \-createdironly " || +{ + cd ${DIRNAME} && + echo Running under ${DIRNAME} && + exec ./${PROGRAM##*/} ${*} || + echo PROBLEM. Cannot create directory ${DIRNAME}, make sure you have the proper permissions to create it and try again +} diff --git a/net/linux-edonkey-core/pkg-comment b/net/linux-edonkey-core/pkg-comment new file mode 100644 index 000000000000..ee94e3fad6f4 --- /dev/null +++ b/net/linux-edonkey-core/pkg-comment @@ -0,0 +1 @@ +eDonkey2000 'core' command line client diff --git a/net/linux-edonkey-core/pkg-descr b/net/linux-edonkey-core/pkg-descr new file mode 100644 index 000000000000..16c9c6962ea4 --- /dev/null +++ b/net/linux-edonkey-core/pkg-descr @@ -0,0 +1,10 @@ +The eDonkey2000 'core' is the actual edonkey program which does +everything behind the scenes - connecting to servers, searching, +downloading, uploading, all that stuff. + +The 'core' comes with a very simple text interface (=command line +client), where you can tell it what to do by typing in commands. + +Check http://www.edonkey2000.com/ and the WWW site below. + +WWW: http://users.aber.ac.uk/tpm01/guihome.html diff --git a/net/linux-edonkey-core/pkg-message b/net/linux-edonkey-core/pkg-message new file mode 100644 index 000000000000..49bb236a9a3b --- /dev/null +++ b/net/linux-edonkey-core/pkg-message @@ -0,0 +1,8 @@ + ATTENTIONATTENTION: + +Please make sure that you read +/usr/local/share/doc/edonkey-core/README.FreeBSD. +It contains important information about both configuring and running +edonkey2000 under FreeBSD. You will have problems running it if you +do not read it. + diff --git a/net/linux-edonkey-core/pkg-plist b/net/linux-edonkey-core/pkg-plist new file mode 100644 index 000000000000..3f5b8784978a --- /dev/null +++ b/net/linux-edonkey-core/pkg-plist @@ -0,0 +1,4 @@ +bin/donkey +bin/donkey-real +%%PORTDOCS%%share/doc/edonkey-core/README.FreeBSD +%%PORTDOCS%%@dirrm share/doc/edonkey-core |