On Fri, 2024-12-20 at 09:55 +0100, Samuel Thibault wrote: > 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.
For many packages that works well, but the devil is in the details. For example, the most common configuration change for chrony is to use a set of custom NTP servers, by dropping a configuration snippet under /etc/chrony/sources.d. But the example config /etc/chrony/chrony.conf always adds the default pool "2.debian.pool.ntp.org" unless you modify the configuration file and comment it out, since the "pool" configuration directive can be used multiple times. I guess this example does not strictly follow this pattern, since the pool setting is the only non-default setting not commented in the file.
