I hate to split hairs on this, but it really does depend on the program in question. I'd say leave it up to the package maintainer to make the call. /etc is hardly pristine on Solaris as shipped from Oracle, with the legacy symbolic links to system binaries and all.
On May 17, 2011, at 6:58 AM, Philip Brown wrote: > Hi folks, > A question has come up, about best pratices for files in etc. Please > give your input. Things can be summarized as follows: > > Some programs require having config files in etc to run. > Some programs *allow* config files in etc, to override defaults. > > Is it better as a general principle, to have *all possible* config > files, exist as both > etc/config.CSW > etc/config (autogenerated from config.CSW) > > or is it better to have the optional ones have their example files > stashed somewhere such as share/doc/prog/config.example, and save the > clutter of not one, but two files, in etc, when they arent usually > needed? > > My own preferences is to avoid unneccessary clutter in etc. > Ben and Dago seem to like clutter :) > > What are other folks' opinions? > _______________________________________________ > maintainers mailing list > [email protected] > https://lists.opencsw.org/mailman/listinfo/maintainers > .:: This mailing list's archive is public. ::. _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
