Don't use inn anymore after migrating to leafnode+
maintaining leafnode+ is more suitable for my home
environment. So I'm looking for somebody who can
test and commit updates and so really maintain the port.
Right now it's difficult to determine if one must upgrade the
currently installed server as the pkg_info reports one has
"inn-stable-v22" installed.
With this patch it's easier to compare the installed version against
/usr/ports/INDEX as the version tag changes when you upgrade the port.
Submitted by: Martti Kuparinen <martti.kuparinen@lmf.ericsson.se>
Don't install rnews setgid uucp by default - the INN maintainers don't
recommend this binary run with privileges because it is not secure.
Anyone who needs the ability to fetch news via UUCP can rebuild the port
with WITH_UUCP_SECURITY_HOLE defined.
</security-officer>
Correct typo from 1.33 which made rnews setuid news, not setgid uucp which it actually
required to implement the intended change.
Submitted by: Russ Allbery <rra@STANFORD.EDU> (first change) via Bugtraq
of my homepage. ISC only makes a few version availabe for ftp
download, so I'd have to update the port every 3 or 4 weeks.
Such an update interval is too heavy for me at the moment.
FWIW, checkout of these things took 5+hrs, staying on the local
.freebsd.org net w/o hitting the 'net at all.
As promised,
$ time cvs ci
real 67m51.701s
user 0m1.250s
sys 0m5.345s
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.
