>> The additional configuration is often too ambiguous.   think a good thing
>> here would be to add MESSAGE files to _all_ pkgs which need manual setup.
>> (Many of them don't, yet.)  That way the clue is handed to the user on
>> pkg_add.

>Yeah, but still, manual intervention is needed - not nice for newbie type
>users. ("What, vi?!")

I agree - for /etc/services and inetd.conf at least.
My own configs tool (for installing stuff on *NIX machines) does 
things like:

[from sslrshd.list]
.if missing $DESTDIR/usr/local/libexec/SSLrshd
# 1st time only
/etc/ssl.users 00644 root bin file no
/usr/local/libexec/SSLrshd 0755 root bin file shell \
 instsvc.sh sshell 614,SSLshell tcp root /usr/local/libexec/SSLrshd SSLrshd -L
.else
# make sure its up to date
/usr/local/libexec/SSLrshd 0755 root bin file no
.endif

The first time that SSLrshd is installed instsvc.sh is invoked to
create an appropriate entry in $DESTDIR/etc/services and 
$DESTDIR/etc/inetd.conf, it does nothing if the file contains
an entry for the service named.

The above approach is used for any service we add that needs
inetd.conf entries, and has been used to install junk on 100's
of *NIX boxen without problems.

For the same reason (supporting multiple *NIX) I'm very anti 
editing /etc/rc*, - see my raves in favour of separate start/stop scripts
the archives should have a few so I won't wast band-width...

--sjg