aboutsummaryrefslogtreecommitdiff
path: root/news/leafnode+
diff options
context:
space:
mode:
authorSteve Price <steve@FreeBSD.org>1999-04-03 01:01:15 +0000
committerSteve Price <steve@FreeBSD.org>1999-04-03 01:01:15 +0000
commit07601d1674c6cd9e7b78e628472b3ddfefdf1258 (patch)
tree2570633973a8013ce1adf884abfc61560058f23d /news/leafnode+
parent638af7f67e0b2c7d249d41edc8e811f19360b307 (diff)
downloadports-07601d1674c6cd9e7b78e628472b3ddfefdf1258.tar.gz
ports-07601d1674c6cd9e7b78e628472b3ddfefdf1258.zip
Update to version 2.6.
PR: 9865 Submitted by: Tom Hukins <tom@eborcom.com>
Notes
Notes: svn path=/head/; revision=17570
Diffstat (limited to 'news/leafnode+')
-rw-r--r--news/leafnode+/Makefile11
-rw-r--r--news/leafnode+/distinfo2
-rw-r--r--news/leafnode+/files/patch-aa2
-rw-r--r--news/leafnode+/files/patch-ab58
-rw-r--r--news/leafnode+/pkg-comment2
5 files changed, 42 insertions, 33 deletions
diff --git a/news/leafnode+/Makefile b/news/leafnode+/Makefile
index e94bea7fdb03..22bae1b516a8 100644
--- a/news/leafnode+/Makefile
+++ b/news/leafnode+/Makefile
@@ -1,15 +1,14 @@
# New ports collection makefile for: leafnode+
-# Version required: 2.3
+# Version required: 2.6
# Date created: 19 November 1998
# Whom: Tom Hukins <tom@eborcom.com>
#
-# $Id: Makefile,v 1.2 1998/12/28 23:19:50 mph Exp $
+# $Id: Makefile,v 1.3 1999/01/10 18:10:09 steve Exp $
#
-DISTNAME= leafnode+-2.3
+DISTNAME= leafnode+-2.6
CATEGORIES= news
-MASTER_SITES= ftp://ftp.big.or.jp/pub/usr2/jam/leafnode/ \
- ftp://ftp.win.or.jp/pub/network/news/misc/
+MASTER_SITES= ftp://ftp.big.or.jp/pub/usr2/jam/leafnode/
MAINTAINER= tom@eborcom.com
@@ -29,7 +28,7 @@ do-install:
.for file in leafnode fetchnews texpire checkgroups leaftool
@${INSTALL_PROGRAM} ${WRKSRC}/${file} ${PREFIX}/sbin
.endfor
-.for file in checkgroups.8 fetchnews.8 leafnode.8 texpire.8
+.for file in ${MAN8}
@${INSTALL_MAN} ${WRKSRC}/${file} ${PREFIX}/man/man8
.endfor
.if !defined{NOPORTDOCS}
diff --git a/news/leafnode+/distinfo b/news/leafnode+/distinfo
index af920aa8226f..cc12be5c5fff 100644
--- a/news/leafnode+/distinfo
+++ b/news/leafnode+/distinfo
@@ -1 +1 @@
-MD5 (leafnode+-2.3.tar.gz) = b6c27866f888c8f916689a640bdd3733
+MD5 (leafnode+-2.6.tar.gz) = 35e9714b0dc0d3e17cbb988497244e6a
diff --git a/news/leafnode+/files/patch-aa b/news/leafnode+/files/patch-aa
index 96e37a2528c2..8433e0f7b7b2 100644
--- a/news/leafnode+/files/patch-aa
+++ b/news/leafnode+/files/patch-aa
@@ -10,7 +10,7 @@
-BINDIR = /usr/local/sbin
-MANDIR = /usr/local/man
+BINDIR = $(PREFIX)/sbin
- VERSION = 2.3
+ VERSION = 2.6
#
# if you want to use Socks, use following
@@ -27,7 +24,7 @@
diff --git a/news/leafnode+/files/patch-ab b/news/leafnode+/files/patch-ab
index b53c4658a7bb..80cbdf691b85 100644
--- a/news/leafnode+/files/patch-ab
+++ b/news/leafnode+/files/patch-ab
@@ -1,7 +1,7 @@
---- FAQ.orig Sun Dec 6 19:37:53 1998
-+++ FAQ Wed Dec 9 17:36:30 1998
-@@ -21,17 +21,17 @@
- 3. How do I configure Leafnode+?
+--- FAQ.orig Fri Jan 29 13:01:52 1999
++++ FAQ Sat Jan 30 22:17:12 1999
+@@ -41,8 +41,8 @@
+ 5. How do I configure Leafnode+?
See the manual pages for information on how to configure Leafnode+.
-Also, see the sample configuration file, "config.example", in the
@@ -10,25 +10,35 @@
+!!PREFIX!!/share/doc/leafnode+.
- 4. How do I upgrade from Leafnode?
+ 6. How do I upgrade from Leafnode?
+@@ -50,8 +50,8 @@
+ Upgrading is easy - Leafnode+ can be used as a direct replacement
+ for Leafnode. However, Leafnode+ will write some additional files in
+ the LIBDIR defined when compiling Leafnode+, usually
+-/usr/lib/leafnode. Therefore, the UID under which Leafnode+ runs,
+-usually root or news, needs write access to this directory.
++!!PREFIX!!/lib/leafnode. Therefore, the UID under which Leafnode+
++runs, usually root or news, needs write access to this directory.
- Upgrading is easy - Leafnode+ can be used as a direct replacement for
- Leafnode. However, Leafnode+ will write some additional files in the
--LIBDIR defined when compiling Leafnode+, usually /usr/lib/leafnode.
--Therefore, the UID under which Leafnode+ runs, usually root or news,
--needs write access to this directory.
-+LIBDIR defined when compiling Leafnode+, !!PREFIX!!/lib/leafnode.
-+Therefore, the UID under which Leafnode+ runs, usually news, needs write
-+access to this directory.
+ You will need to change all references to the "fetch" program to
+ refer to "fetchnews". The name of this program has changed because
+@@ -59,8 +59,8 @@
+ "fetchnews" describes the function of the program better.
+ To update from Cornelius's Leafnode, copy
+-/var/spool/news/leaf.node/groupinfo into your LIBDIR (usually
+-/usr/lib/leafnode/groupinfo) then run "fetchnews".
++/var/spool/news/leaf.node/groupinfo into your LIBDIR
++(!!PREFIX!!/lib/leafnode/groupinfo) then run "fetchnews".
- 5. Can I use Leafnode+ with multiple news servers?
-@@ -61,7 +61,7 @@
+
+ 7. Can I use Leafnode+ with multiple news servers?
+@@ -90,7 +90,7 @@
Most news reader software uses the NEWGROUPS command to learn about
- the creation of new groups. The Leafnode+ news server does not
- support this command. To check if new groups are available, see the
+ the creation of new groups. The Leafnode+ news server does not
+ support this command. To check if new groups are available, see the
-"groupinfo" file in your LIBDIR (usually /usr/lib/leafnode).
-+"groupinfo" file in your LIBDIR (usually !!PREFIX!!/lib/leafnode).
++"groupinfo" file in your LIBDIR (!!PREFIX!!/lib/leafnode).
@@ -38,14 +48,14 @@
3. make installall
--5. Edit $(LIBDIR)/config so server points to your upstream news server
-+5. Edit !!PREFIX!!/lib/leafnode/config so the server points to your
+-4. Edit $(LIBDIR)/config so server points to your upstream news server
++4. Edit !!PREFIX!!/lib/leafnode/config so the server points to your
+ upstream news server
(generally, your IP provider's). Make sure $NNTPSERVER or
/etc/nntpserver points to your own host so clients will talk to
leafnode rather than try to go to the upstream server.
@@ -15,25 +16,24 @@
- 4. Set up a cron job (as user "news") to run texpire every night or
+ 5. Set up a cron job (as user "news") to run texpire every night or
maybe every week. Here is my crontab line, which runs nightly:
-0 4 * * * /usr/local/sbin/texpire
@@ -59,16 +69,16 @@
tells cron to run texpire at 4am Monday morning.
- 5. Make sure fetchnews is run at the appropriate time. If you have a
+ 6. Make sure fetchnews is run at the appropriate time. If you have a
full-time link, run it out of cron (as "news" again), if not, run
it when your connection to the net is established. If it is run as
- root, it will change user to "news". I use PPP, and run fetchnews
- from /etc/ppp/ip-up.
+ root, it will change user to "news".
--6. Edit /etc/inetd.conf so $(BINDIR)/leafnode is executed for incoming
+-7. Edit /etc/inetd.conf so $(BINDIR)/leafnode is executed for incoming
- NNTP connections. HUP inetd. Here is my inetd.conf line:
-+6. Edit /etc/inetd.conf so !!PREFIX!!/sbin/leafnode is executed for
++7. Edit /etc/inetd.conf so !!PREFIX!!/sbin/leafnode is executed for
+ incoming NNTP connections. HUP inetd. Here is my inetd.conf line:
-nntp stream tcp nowait news /usr/local/sbin/leafnode
diff --git a/news/leafnode+/pkg-comment b/news/leafnode+/pkg-comment
index c44486897600..9f0a5a992975 100644
--- a/news/leafnode+/pkg-comment
+++ b/news/leafnode+/pkg-comment
@@ -1 +1 @@
-Leafnode+ is a multi-user offline news package for small sites.
+Multi-user offline Usenet news package for small sites.