Josh Triplett, le jeu. 19 déc. 2024 19:05:56 -0800, a ecrit: > Samuel Thibault wrote: > > Ansgar 🙀, le jeu. 19 déc. 2024 16:21:03 +0100, a ecrit: > > > And it is actively harmful as if one edits the example configuration to > > > have a useful configuration as dpkg will start annoying admins with > > > "the example configuration has changed; what do you want to do" > > > messages. > > > > Yes, but the thing is: I *do* want to see that message, to make sure > > what changed upstream and fix my manual configuration accordingly. > > There are (at least) two different models of handling configuration > here; people used to one model find the other to be awkward and cause > problems, and vice versa. > > In the model where you augment the default system configuration by > adding files in /etc, you ideally don't *need* a complete copy of the > configuration file.
Yes, that's why having both the ready-to-be-modified model *and* a .d/ directory fits both cases. > Then, we could have a package (e.g. "etc-commented-defaults") with an > on-installation trigger for that location, which automatically copies > over the defaults to /etc if they don't already exist, updates them if > they match the defaults, and (ideally) has a ucf-style mechanism for the > case where they've been changed. But isn't it what we already have? If I don't modify the example in /etc and only add files to .d/, I'm getting upgrades without questions. And if I modify the example in /etc, I'm getting the question. That way I can decide per-package whether to just augment or change the default configuration. > That seems like an improvement over the current situation, in which > there's a mix of packages that ship commented-defaults (causing problems > for the people who want an empty /etc) and packages that don't (causing > problems for the people who expect a sample file in /etc). But the assumption is the same in both case: packages should provide an example file in a standardized place. Be it in /etc or in some /usr/share/ doesn't change the question of having people converging to it. And having it ready for modification in /etc is way more convenient than having it in some /usr/share and determining where it's supposed to be put in /etc. Samuel
