Daniel Gröber <d...@darkboxed.org> writes: > Debian policy section 10.7.2:
>> Any configuration files created or *used* by your package must reside in >> /etc, [...] > (Emphasis mine) Policy has a specific definition of configuration file, which makes your point here somewhat ambiguous, but I can understand this misreading and therefore think this is a bug in Policy that we should fix. It has certainly never been the case that every file loaded by a binary that controls operation of that binary was required to be in /etc, and I can name numerous packages that predate and are not attempting to follow the empty-/etc configuration model (such as zsh, autoconf, inn2, and every package that loads *.desktop files) as obvious cases of loading configuration information from /usr. The intended principle here is that configuration files *that may be edited by a system administrator* should be in /etc. Not files that are intended to be read-only or configuration information shipped by Debian that the local administrator should not need to edit. That's entirely consistent with a model where the override files edited by the system administrator are in /etc and the defaults they are overriding are somewhere in /usr; Policy doesn't care whether they are hard-coded inside some binary or present on disk in some loadable form. I'll open a bug against debian-policy so that we can clarify the wording and avoid this misreading. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
