aboutsummaryrefslogtreecommitdiff
path: root/net-p2p/linux-edonkey-core
diff options
context:
space:
mode:
Diffstat (limited to 'net-p2p/linux-edonkey-core')
-rw-r--r--net-p2p/linux-edonkey-core/Makefile52
-rw-r--r--net-p2p/linux-edonkey-core/distinfo2
-rw-r--r--net-p2p/linux-edonkey-core/files/README.FreeBSD90
-rw-r--r--net-p2p/linux-edonkey-core/pkg-descr8
-rw-r--r--net-p2p/linux-edonkey-core/pkg-message20
-rw-r--r--net-p2p/linux-edonkey-core/pkg-plist10
6 files changed, 0 insertions, 182 deletions
diff --git a/net-p2p/linux-edonkey-core/Makefile b/net-p2p/linux-edonkey-core/Makefile
deleted file mode 100644
index 472a87075b60..000000000000
--- a/net-p2p/linux-edonkey-core/Makefile
+++ /dev/null
@@ -1,52 +0,0 @@
-# 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= 1.3.0
-PORTEPOCH= 1
-CATEGORIES= net linux
-MASTER_SITES= http://www.zen18864.zen.co.uk/${PORTNAME}/${PORTVERSION}/
-PKGNAMEPREFIX= linux-
-PKGNAMESUFFIX= -core
-DISTNAME= ${PORTNAME}clc_${PORTVERSION}_${ARCH}
-
-MAINTAINER= ports@FreeBSD.org
-COMMENT= eDonkey2000 'core' command line client
-
-ONLY_FOR_ARCHS= i386
-USE_LINUX= yes
-NO_BUILD= yes
-NO_WRKSUBDIR= yes
-
-BINARY_NAME_OLD?= ${PORTNAME}clc
-BINARY_NAME= donkey
-
-DOC_FILES= ChangeLog LISEZMOI README changelog.Debian.gz
-
-pre-install:
- @${BRANDELF} -t Linux ${WRKSRC}/usr/bin/${BINARY_NAME_OLD}
-
-do-install:
- ${INSTALL} -d ${PREFIX}/sbin
- ${INSTALL_PROGRAM} ${WRKSRC}/usr/bin/${BINARY_NAME_OLD} ${PREFIX}/sbin/${BINARY_NAME}
- ${INSTALL} -d ${PREFIX}/share/${PORTNAME}${PKGNAMESUFFIX}
- ${INSTALL_DATA} ${WRKSRC}/usr/share/${PORTNAME}clc/contact.dat ${PREFIX}/share/${PORTNAME}${PKGNAMESUFFIX}/contact.dat
- ${INSTALL_DATA} ${WRKSRC}/usr/share/${PORTNAME}clc/server.met ${PREFIX}/share/${PORTNAME}${PKGNAMESUFFIX}/server.met
-
-post-install:
-.ifndef(NOPORTDOCS)
- ${INSTALL} -d ${DOCSDIR}${PKGNAMESUFFIX}
-
-.for file in ${DOC_FILES}
- ${INSTALL_MAN} ${WRKSRC}/usr/share/doc/${PORTNAME}clc/${file} ${DOCSDIR}${PKGNAMESUFFIX}
-.endfor
-
- ${INSTALL_MAN} ${FILESDIR}/README.FreeBSD ${DOCSDIR}${PKGNAMESUFFIX}
-.endif
- @${SED} -e 's|%%DOCSDIR%%|${DOCSDIR}${PKGNAMESUFFIX}|g' ${PKGMESSAGE}
-
-.include <bsd.port.mk>
diff --git a/net-p2p/linux-edonkey-core/distinfo b/net-p2p/linux-edonkey-core/distinfo
deleted file mode 100644
index a85bfe4c7da7..000000000000
--- a/net-p2p/linux-edonkey-core/distinfo
+++ /dev/null
@@ -1,2 +0,0 @@
-MD5 (edonkeyclc_1.3.0_i386.tar.gz) = 46ced65b8bde60db234ad781861139c8
-SIZE (edonkeyclc_1.3.0_i386.tar.gz) = 740443
diff --git a/net-p2p/linux-edonkey-core/files/README.FreeBSD b/net-p2p/linux-edonkey-core/files/README.FreeBSD
deleted file mode 100644
index b4e4c3d86f33..000000000000
--- a/net-p2p/linux-edonkey-core/files/README.FreeBSD
+++ /dev/null
@@ -1,90 +0,0 @@
-
- 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 'edonkey-gui-gtk' (if you chose
-the FreeBSD native GTK GUI client, or linux-edonkey-gui-gtk if Linux
-one) or 'edonkey-gui-java' (if you chose the Java GUI client). The
-Java GUI is very slow compared to the GTK one but it both supports
-multiple line selections and ed2k link pastes. The GTK one cannot
-do that now but it's very fast; it can accept ed2k link drag-n-drops
-using a mouse and keeps getting new features all the time. Therefore,
-I would advise using both, each for what their strong points are.
-The Java one to multiple select 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/pkg-descr b/net-p2p/linux-edonkey-core/pkg-descr
deleted file mode 100644
index 646b12ef345f..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-descr
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-WWW: http://www.edonkey2000.com/
diff --git a/net-p2p/linux-edonkey-core/pkg-message b/net-p2p/linux-edonkey-core/pkg-message
deleted file mode 100644
index 20694f402081..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-message
+++ /dev/null
@@ -1,20 +0,0 @@
- ATTENTIONATTENTION:
-
-Please make sure that you read
-%%DOCSDIR%%/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.
-
-eDonkey2000 version 0.46 and later store downloads in a different
-format. Therefore, they are not compatible with either lmule or
-older eDonkey2000 clients.
-
-eDonkey2000 version 1.0.2 requires edonkey-gui-gtk version 0.6.3 or higher.
-Older gui versions will not work with this version. Also the standard directory
-in which eDonkey2000 stores the user settings has been changed from
-~/.edonkey2000-core to ~/.eDonkey2000. That's why eDonkey2000 will NOT
-recognise your settings and downloads until you rename the old directory.
-
-Finally, this port doesn't come with a wrapper anymore, because eDonkey2000
-keeps user settings in a directory that is hardcoded into the executable.
diff --git a/net-p2p/linux-edonkey-core/pkg-plist b/net-p2p/linux-edonkey-core/pkg-plist
deleted file mode 100644
index 200c6e792f70..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-plist
+++ /dev/null
@@ -1,10 +0,0 @@
-sbin/donkey
-share/edonkey-core/contact.dat
-share/edonkey-core/server.met
-%%PORTDOCS%%%%DOCSDIR%%-core/README.FreeBSD
-%%PORTDOCS%%%%DOCSDIR%%-core/ChangeLog
-%%PORTDOCS%%%%DOCSDIR%%-core/LISEZMOI
-%%PORTDOCS%%%%DOCSDIR%%-core/README
-%%PORTDOCS%%%%DOCSDIR%%-core/changelog.Debian.gz
-%%PORTDOCS%%@dirrm %%DOCSDIR%%-core
-@dirrm share/edonkey-core