On Wed, 16 Jul 2003, Nick Boyce wrote:

> On Tue, 15 Jul 2003 12:28:15 +0930 (CST), Berndt wrote:
>
> >I would prefer a message to that fact at the end of the installation
> >cycle rather then having the installation process of htdig to mess
> >around witht he apache config files.
>
> I'd settle for that too.

FYI, htdig isn't just for apache. wwwoffle's cache webserver includes
a configuration for htdig that works out-of-the-box. I think, what
you're really suggesting, is that apache use htdig out of the box.
That would seem to require a change to the apache package, or an
add-on, rather than a change to htdig.

> >> 2)  The standard htdig graphics only get installed to
> >> /usr/pkg/share/examples/htdig/, which seems the wrong place - surely
> >> they too would usefully go in /usr/pkg/etc/htdig/.  And there is no
> >> warning of that fact from the installer.
> >
> >Read hier(7). The /etc and /usr/pkg/etc filesystem are set aside for
> >system configuration and script files and not as suggested above for
> >application example files.
>
> OK - I can agree with you there - we should only have config files and
> the like in /etc (and /usr/pkg/etc) - but I suggest that the
> "application example" files are more than just examples for most
> people - they're the actual resources that most htdig installations
> will use for *production*

One of the reasons given, in a discussion long ago, for creating
/usr/pkg/etc and /usr/X11R6/etc ghettos, is that the size of the
accumulation in there would overwhelm the root file-system.
Accordingly, we've been trying to keep things out of there that don't
belong there, with the ultimate goal of restoring all host-specific
configs to their natural place, in /etc. Whether you buy that or not,
we only copy files that the administrator is likely to customize into
{/usr/pkg,}/etc. We don't install and register anything directly into
there, as that would cause a package upgrade to wipe out the current,
working configuration.

Frederick