On Wed, Jul 21, 2021 at 12:36:40PM +0100, Daniel P. Berrangé wrote: > On Wed, Jul 21, 2021 at 03:16:39AM -0700, Andrea Bolognani wrote: > > In particular, I worry about changes in defaults being more difficult > > for users to detect: in Debian at least, changes to the default > > sysconfig files result in the admin being given the possibility to > > review and tweak their local customizations at package upgrade time, > > and by moving the defaults off to the .service files we're losing > > that convenience. I understand other distros don't have the same > > tooling around configuration files, but still it feels like a step > > backwards in this regard. > > Debian needs that interactive UI for reviewing changes precisely > because users are being made to modify files that are shipped by > the package, and that needs to be addressed synchronously with > the upgrade in some manner. > > If we remove the sysconfig files, we're not expecting users to > modify the .service files. Instead they will be using the systemd > overrides in /etc/systemd/system/libvirtd.service.d/<blah> to > customize. > > They'll still potentially want to review your overrides after > upgrading, but you'll not be forced todo so in the middle of > the package upgrade transaction, since they're not modifying > a file owned by the package That's still going to be the case for other configuration files, such as anything in /etc/libvirt/, so dropping the sysconfig files is not going to change things significantly. -- Andrea Bolognani / Red Hat / Virtualization
