Samuel Thibault <sthiba...@debian.org> writes: > It seems way more often to me that I want to easily inspect/modify/amend > the configuration in /etc (without having to look whatever other place > to find out about the default configuration) than checking what changes > I have made to /etc which I may not want any more. And thus having a > special program for the latter looks completely fine to me. That's what > people do with etckeeper and such already.
And this is the root of the problem: you want one thing for understandable reasons, and other people, like myself, would prefer the opposite behavior of having /etc empty by default for different understandable reasons. We both understand the other's point of view and simply disagree about the merits of the features of the two methods. Neither side of this preference is going to convince the other any more than I am going to convince everyone to use Emacs, and yet every time we have this discussion it turns into an extended effort to convince people with the opposite preference. Maybe it would be more productive to take the preference disagreement as given and then try to figure out how to proceed given that we're never going to all agree on the best way of handling configuration files? Is there some way that we can try to accomodate both groups? -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
