Henrik Ahlgren, le ven. 20 déc. 2024 11:32:37 +0200, a ecrit: > 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.
It will be with any scheme that gets devised. So the simpler scheme will be better. > 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. And that will get troubles with other schemes too. One thing that could be useful is to be able to tell dpkg "never ask me again for replacing this config file with the shipped one", and you will get what is being proposed. Per-package. Samuel
