Filesystem Hierarchy Standard (FHS) compliancy?

[James Ralston]

On 11 Aug 2000, Miquel van Smoorenburg wrote:

> By using Debian [to simplify the maintenance and >upgrading of
> config files], I suppose, since dpkg does this better than rpm ;)

Sorry, I'm not well-versed enough in dpkg for religious arguments yet.
;)  (Red Hat's %config and %config(noreplace) options have been
adequate so far for me, but dpkg might honestly have a better
approach.  I'm not completely sure.)

> inshellvars* aren't config files, they are supposed to be static
> (i.e. /usr/lib material, or even /usr/share [yuck])

Well, they're config files in the sense that they hold INN
configuration information, but yes, they're also static.  I would
tentatively argue that their "config" nature should be the primary
factor in determining where to place them, but I can certainly see
arguments for /usr/lib/inn or /usr/share/inn.

(And if the choice were between /usr/lib/inn and /usr/share/inn, I'd
prefer /usr/lib/inn--the files themselves are architecture-independent
and non-executable, but they can be viewed more as a modules for their
respective languages, which would place them into /usr/lib/inn.)

James