1994-10-23 01:42:21 +00:00
|
|
|
# New ports collection makefile for: inn
|
1999-09-11 11:25:28 +00:00
|
|
|
# Version required: 2.2
|
1996-12-18 23:32:28 +00:00
|
|
|
# Date created: 20 Oct 1994 (1.4), 18 Dec 1996 (1.5.1)
|
1994-10-23 01:42:21 +00:00
|
|
|
# Whom: torstenb
|
|
|
|
|
#
|
1999-08-30 14:33:04 +00:00
|
|
|
# $FreeBSD$
|
1994-10-23 01:42:21 +00:00
|
|
|
|
2000-02-26 11:01:29 +00:00
|
|
|
DISTNAME= inn-STABLE_2_2-2000-02-25_03-09
|
1999-02-16 22:01:06 +00:00
|
|
|
PKGNAME= inn-stable-v22
|
1996-11-18 11:44:27 +00:00
|
|
|
CATEGORIES= news
|
2000-02-08 09:29:51 +00:00
|
|
|
MASTER_SITES= http://people.FreeBSD.org/~andreas/download/ \
|
1999-08-21 17:13:39 +00:00
|
|
|
ftp://ftp.isc.org/isc/inn/snapshots/
|
1996-06-24 21:52:30 +00:00
|
|
|
|
1999-08-31 06:53:31 +00:00
|
|
|
MAINTAINER= andreas@FreeBSD.org
|
1995-05-04 22:39:46 +00:00
|
|
|
|
1999-02-24 23:27:16 +00:00
|
|
|
Y2K= http://www.isc.org/inn-y2k.html
|
|
|
|
|
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
.if defined(BATCH)
|
|
|
|
|
# in BATCH mode we use the default
|
|
|
|
|
NEWSSPOOL=/var/spool/news
|
1999-04-10 19:57:59 +00:00
|
|
|
NEWSLIB=${PREFIX}/news
|
|
|
|
|
NEWSLOG=/var/log/news
|
|
|
|
|
NEWSMAN=${PREFIX}/man
|
|
|
|
|
NEWSINFO=${PREFIX}/info
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
.else
|
|
|
|
|
# you can set this in /etc/make.conf !
|
|
|
|
|
NEWSSPOOL?=/var/spool/news
|
1999-04-10 19:57:59 +00:00
|
|
|
NEWSLIB?=${PREFIX}/news
|
|
|
|
|
NEWSLOG?=/var/log/news
|
|
|
|
|
NEWSMAN?=${PREFIX}/man
|
|
|
|
|
NEWSINFO?=${PREFIX}/info
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
.endif
|
|
|
|
|
|
1999-02-16 22:01:06 +00:00
|
|
|
HAS_CONFIGURE= yes
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
CONFIGURE_ARGS+=--with-spool-dir=${NEWSSPOOL}
|
1999-04-10 19:57:59 +00:00
|
|
|
CONFIGURE_ARGS+=--prefix=${NEWSLIB}
|
|
|
|
|
CONFIGURE_ARGS+=--with-log-dir=${NEWSLOG}
|
|
|
|
|
CONFIGURE_ARGS+=--mandir=${NEWSMAN}
|
|
|
|
|
CONFIGURE_ARGS+=--infodir=${NEWSINFO}
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
|
|
|
|
|
# tmp- and spool-dir have to live on the same filesystem, to avoid this error:
|
|
|
|
|
# "rnews: cant rename /tmp/36d24c3ehN1072
|
|
|
|
|
# to /var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
|
|
|
|
|
CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
|
1999-01-13 04:17:38 +00:00
|
|
|
|
1999-02-16 22:01:06 +00:00
|
|
|
# Highly recommended, because many of the really good spam filters
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
# are written in Perl (from the author)
|
1999-02-16 22:01:06 +00:00
|
|
|
CONFIGURE_ARGS+=--with-perl
|
|
|
|
|
# if server has less than 256 MB RAM
|
|
|
|
|
CONFIGURE_ARGS+=--enable-tagged-hash
|
|
|
|
|
# Do not create static libraries
|
|
|
|
|
CONFIGURE_ARGS+=--disable-static
|
1996-12-18 23:32:28 +00:00
|
|
|
|
1999-02-16 22:01:06 +00:00
|
|
|
# Most available filters seem to be written in Perl these days,
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
# so you can safely leave out TCL support (from the author)
|
1999-02-16 22:01:06 +00:00
|
|
|
#CONFIGURE_ARGS+=--with-tcl
|
1999-04-10 19:57:59 +00:00
|
|
|
|
1999-02-16 22:01:06 +00:00
|
|
|
# Do not create shared libraries
|
|
|
|
|
#CONFIGURE_ARGS+=--disable-shared
|
1996-12-18 23:32:28 +00:00
|
|
|
|
1999-02-16 22:01:06 +00:00
|
|
|
MAN1= convdate.1 getlist.1 grephistory.1 inews.1 innconfval.1 innfeed.1 \
|
|
|
|
|
installit.1 nntpget.1 rnews.1 shlock.1 shrinkfile.1 startinnfeed.1 \
|
|
|
|
|
subst.1
|
|
|
|
|
MAN3= clientlib.3 dbz.3 inndcomm.3 libinn.3 libstorage.3 parsedate.3 qio.3 \
|
|
|
|
|
wildmat.3
|
|
|
|
|
MAN5= active.5 control.ctl.5 cycbuff.conf.5 distrib.pats.5 expire.ctl.5 \
|
|
|
|
|
history.5 incoming.conf.5 inn.conf.5 innfeed.conf.5 innwatch.ctl.5 \
|
|
|
|
|
moderators.5 motd.news.5 newsfeeds.5 newslog.5 nnrp.access.5 \
|
|
|
|
|
nnrpd.track.5 nntpsend.ctl.5 overview.ctl.5 overview.fmt.5 \
|
|
|
|
|
passwd.nntp.5 storage.conf.5 storage.ctl.5
|
|
|
|
|
MAN8= actived.8 actsync.8 actsyncd.8 archive.8 batcher.8 buffchan.8 \
|
|
|
|
|
cnfsstat.8 controlchan.8 crosspost.8 ctlinnd.8 cvtbatch.8 expire.8 \
|
|
|
|
|
expireindex.8 expireover.8 expirerm.8 fastrm.8 filechan.8 inncheck.8 \
|
|
|
|
|
innd.8 inndf.8 innreport.8 innstat.8 innwatch.8 innxbatch.8 innxmit.8 \
|
|
|
|
|
mailpost.8 makeactive.8 makehistory.8 news-recovery.8 news.daily.8 \
|
|
|
|
|
news2mail.8 newslog.8 newsrequeue.8 nnrpd.8 nntpsend.8 overchan.8 \
|
|
|
|
|
pgpverify.8 prunehistory.8 pullnews.8 scanlogs.8 send-uucp.8 sm.8 \
|
|
|
|
|
tally.control.8 tally.unwanted.8 writelog.8
|
1995-10-25 02:12:08 +00:00
|
|
|
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
pre-extract:
|
|
|
|
|
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
|
1999-04-10 19:57:59 +00:00
|
|
|
@${ECHO} ">> building inn2 with NEWSLIB=${NEWSLIB}..."
|
|
|
|
|
@${ECHO} ">> building inn2 with NEWSLOG=${NEWSLOG}..."
|
|
|
|
|
@${ECHO} ">> building inn2 with NEWSMAN=${NEWSMAN}..."
|
|
|
|
|
@${ECHO} ">> building inn2 with NEWSINFO=${NEWSINFO}..."
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
|
1994-10-23 01:42:21 +00:00
|
|
|
pre-install:
|
1999-04-10 19:57:59 +00:00
|
|
|
.for dir in ${NEWSSPOOL} ${NEWSLIB} ${NEWSLOG} ${NEWSMAN} ${NEWSINFO}
|
|
|
|
|
${MKDIR} ${dir}
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${dir}
|
1999-04-10 19:57:59 +00:00
|
|
|
.endfor
|
1995-05-04 22:39:46 +00:00
|
|
|
|
1995-10-06 14:33:05 +00:00
|
|
|
update: build
|
|
|
|
|
@(cd ${WRKSRC} ; ${MAKE} ${MAKE_FLAGS} ${MAKEFILE} update)
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
@${MAKE} ${.MAKEFLAGS} compress-man
|
1995-10-06 14:33:05 +00:00
|
|
|
@${MAKE} ${.MAKEFLAGS} post-install
|
|
|
|
|
|
1995-05-04 22:39:46 +00:00
|
|
|
post-install:
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/articles
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/articles
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/cycbuffs
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/cycbuffs
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/incoming/bad
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/incoming/bad
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/innfeed
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/innfeed
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/outgoing
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/outgoing
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/overview
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/overview
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/tmp
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/tmp
|
updated inn2 to last recent STABLE version
inn-STABLE_2_2-1999-02-17_03-02
introduced new variable NEWSSPOOL, which points to news spooldir...
- can be fine-tuned in /etc/make.conf
- can be overwritten on the commandline
- defaults to /var/spool/news, when not set
- is set to /var/spool/news, when in port building (BATCH) mode
bugfix: tmp- and spool-dir have to live on the same filesystem, to avoid
this error:
"rnews: cant rename /tmp/36d24c3ehN1072 to
/var/spool/news/incoming/36d24c3eTg1072 Cross-device link"
Solution -> CONFIGURE_ARGS+=--with-tmp-path=${NEWSSPOOL}/tmp
added two comments "(from the author)", to reflect that I'm not personally
focussed on perl
Some (early) output in the pre-extract phase, to tell the admin, where
our news-spool will live:
@${ECHO} ">> building inn2 with NEWSSPOOL=${NEWSSPOOL}..."
Create ${PREFIX}/news and ${NEWSSPOOL}/news with proper permissions
in pre-install target
Since we took care about creation of spool-dir in pre-install, we can
now safely perform the ${MKDIR}'s in post-install target
${MKDIR} creates ${NEWSSPOOL}/incoming/bad and ${NEWSSPOOL}/incoming at the
same time, so save some CPU cycles
Fixed update target, manual pages will be compressed now by performing
a "compress-man" as well (we had "up to date" uncompressed and
old compressed manpages, which is kinda sub-optimal ;-)
Well people, I think now we have a real fine inn port.
I'd like to ask the inn port maintainer, if we should remove
inn, since it's a bit outdated.
The new inn2 offers many new features and you have the possibility
to change inn's runtime behaviour in config files, instead of
recompiling it.
Then I think, that the old inn isn't maintained anymore by ISC.
1999-02-23 19:33:07 +00:00
|
|
|
${MKDIR} -m 0775 ${NEWSSPOOL}/uniover
|
1999-09-11 11:25:28 +00:00
|
|
|
${CHOWN} news:news ${NEWSSPOOL}/uniover
|
1998-08-16 18:56:32 +00:00
|
|
|
${SED} <${FILESDIR}/innd.sh >${PREFIX}/etc/rc.d/innd.sh \
|
1999-08-22 19:01:07 +00:00
|
|
|
s+!!PREFIX!!+${PREFIX}+g && ${CHMOD} +x ${PREFIX}/etc/rc.d/innd.sh
|
1999-12-26 14:20:49 +00:00
|
|
|
# create log and run subdir with a .keep_me file to make sure
|
|
|
|
|
# packaging works. The mkdir might be unnecessary, but to be sure ...
|
|
|
|
|
.for dir in log run
|
|
|
|
|
${MKDIR} -p ${NEWSLIB}/${dir}
|
|
|
|
|
touch ${NEWSLIB}/${dir}/.keep_me
|
|
|
|
|
.endfor
|
1999-02-16 22:07:51 +00:00
|
|
|
# make rnews work when getting news via uucp !
|
1999-08-22 19:01:07 +00:00
|
|
|
${CHMOD} 4555 ${NEWSLIB}/bin/rnews
|
1994-10-23 01:42:21 +00:00
|
|
|
|
|
|
|
|
.include <bsd.port.mk>
|