summaryrefslogtreecommitdiff
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/Makefile58
-rw-r--r--net-p2p/linux-edonkey-core/distinfo1
-rw-r--r--net-p2p/linux-edonkey-core/files/README.FreeBSD94
-rw-r--r--net-p2p/linux-edonkey-core/files/wrapper.sh23
-rw-r--r--net-p2p/linux-edonkey-core/pkg-descr10
-rw-r--r--net-p2p/linux-edonkey-core/pkg-message12
-rw-r--r--net-p2p/linux-edonkey-core/pkg-plist4
7 files changed, 0 insertions, 202 deletions
diff --git a/net-p2p/linux-edonkey-core/Makefile b/net-p2p/linux-edonkey-core/Makefile
deleted file mode 100644
index 65537dc8f6a8..000000000000
--- a/net-p2p/linux-edonkey-core/Makefile
+++ /dev/null
@@ -1,58 +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= 0.50.1
-PORTEPOCH= 1
-CATEGORIES= net linux
-MASTER_SITES= http://www.overnet.com/files/
-PKGNAMEPREFIX= linux-
-PKGNAMESUFFIX= -core
-DISTNAME= donkey${PORTVERSION}
-
-MAINTAINER= lioux@FreeBSD.org
-COMMENT= eDonkey2000 'core' command line client
-
-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_OLD?= donkey${PORTVERSION}
-BINARY_NAME= donkey
-
-post-patch:
- @${SED} -e "s|%%PREFIX%%|${PREFIX}|" ${FILESDIR}/wrapper.sh > \
- ${WRKDIR}/wrapper.sh
-
-do-install:
- @${INSTALL_PROGRAM} ${WRKSRC}/${BINARY_NAME_OLD} ${PREFIX}/sbin/${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.pre.mk>
-
-pre-install:
-.if exists(${STRIP_CMD})
- @${STRIP_CMD} ${WRKSRC}/${BINARY_NAME_OLD}
-.endif
- @${BRANDELF} -t Linux ${WRKSRC}/${BINARY_NAME_OLD}
-
-.include <bsd.port.post.mk>
diff --git a/net-p2p/linux-edonkey-core/distinfo b/net-p2p/linux-edonkey-core/distinfo
deleted file mode 100644
index 8d23538c0980..000000000000
--- a/net-p2p/linux-edonkey-core/distinfo
+++ /dev/null
@@ -1 +0,0 @@
-MD5 (donkey0.50.1.tar.gz) = dcda1d56faf30e63765d4206faff1168
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 8fe970822fc3..000000000000
--- a/net-p2p/linux-edonkey-core/files/README.FreeBSD
+++ /dev/null
@@ -1,94 +0,0 @@
-[ 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 '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/files/wrapper.sh b/net-p2p/linux-edonkey-core/files/wrapper.sh
deleted file mode 100644
index a1cbdc0258a2..000000000000
--- a/net-p2p/linux-edonkey-core/files/wrapper.sh
+++ /dev/null
@@ -1,23 +0,0 @@
-#!/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}/sbin/${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-descr b/net-p2p/linux-edonkey-core/pkg-descr
deleted file mode 100644
index 16c9c6962ea4..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-descr
+++ /dev/null
@@ -1,10 +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.
-
-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
deleted file mode 100644
index e67c43fee822..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-message
+++ /dev/null
@@ -1,12 +0,0 @@
- 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.
-
-eDonkey2000 version 0.46 and later store downloads in a different
-format. Therefore, they are not compatible with either lmule or
-older eDonkey2000 clients.
-
diff --git a/net-p2p/linux-edonkey-core/pkg-plist b/net-p2p/linux-edonkey-core/pkg-plist
deleted file mode 100644
index b500e2c37b31..000000000000
--- a/net-p2p/linux-edonkey-core/pkg-plist
+++ /dev/null
@@ -1,4 +0,0 @@
-bin/donkey
-sbin/donkey-real
-%%PORTDOCS%%share/doc/edonkey-core/README.FreeBSD
-%%PORTDOCS%%@dirrm share/doc/edonkey-core