On Wed, Jul 21, 2021 at 03:16:39AM -0700, Andrea Bolognani wrote: > On Tue, Jul 20, 2021 at 07:00:20PM +0200, Olaf Hering 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 Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
