aboutsummaryrefslogtreecommitdiffstats
path: root/news/inn-stable/distinfo
diff options
context:
space:
mode:
authorandreas <andreas@FreeBSD.org>1999-02-24 03:33:07 +0800
committerandreas <andreas@FreeBSD.org>1999-02-24 03:33:07 +0800
commite3ab327008a2593dc43de3c729113e157add0058 (patch)
tree8154838ec7f12bcc6be53a0864b062e4f10fe618 /news/inn-stable/distinfo
parenta7a5a056ebfa069c70b0d9da3c0a24c332eb06c2 (diff)
downloadfreebsd-ports-gnome-e3ab327008a2593dc43de3c729113e157add0058.tar.gz
freebsd-ports-gnome-e3ab327008a2593dc43de3c729113e157add0058.tar.zst
freebsd-ports-gnome-e3ab327008a2593dc43de3c729113e157add0058.zip
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.
Diffstat (limited to 'news/inn-stable/distinfo')
-rw-r--r--news/inn-stable/distinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/news/inn-stable/distinfo b/news/inn-stable/distinfo
index cba673c0daed..f38ea451fcfa 100644
--- a/news/inn-stable/distinfo
+++ b/news/inn-stable/distinfo
@@ -1 +1 @@
-MD5 (inn-STABLE_2_2-1999-02-14_03-02.tar.gz) = b8fdc29a35551f1dd4c31e46026755aa
+MD5 (inn-STABLE_2_2-1999-02-17_03-02.tar.gz) = ca0d3c748bb4289a7380702359be4120