Julien ÉLIE <jul...@trigofacile.com> writes:
>> Yeah, I'm inclined to agree with this, and wonder if INN should change
>> its upstream behavior to install a sample in a path other than the one
>> used by innd and nnrpd.
> That would also be fine, yes.
> Couldn't we install them as ${PATHETC}/motd.innd.sample and
> ${PATHETC}/motd.nnrpd.sample or should they be in a separate path?
> In the latter case, would the ${PATHETC}/samples directory be fine?
Looking at the files, they're mostly documentation for the facility. I'm
wondering whether that's a useful thing to install. The upside of
installing some sort of sample is that it makes it clear to people
installing a new server that this is something that can be done. The
downside is that the files are not, themselves, actually useful; you
wouldn't use any part of their content when creating a real MOTD file.
They're just documentation.
That makes me feel like handling the documentation some other way, such as
pointers in INSTALL, may be a better idea than installing the sample file.
On second thought, installing them in a separate samples directory means
they aren't obviously there when someone is setting up a new server, so it
seems to eliminate most of the upside and add some additional complexity.
> Shouldn't we do the same for the ${PATHETC}/subscriptions file? It
> already contains a list of newsgroups.
Yeah, but it's a fairly innocuous one that's been the same for many years.
There's not much there that will really hurt anything, so I'd be inclined
to leave that one alone.
> What for files like ${PATHETC}/actsync.ign? Maybe the default behaviour
> is not the expected one.
It's not a horrible default, though. It seems pretty safe to me.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
