On 12/21/21 04:22, Olaf Hering wrote:
Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
---
NEWS.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index e7d5316721..9255113df4 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -44,6 +44,16 @@ v8.0.0 (unreleased)
* **Improvements**
I noticed previous releases include a "Packaging changes" section to announce
this type of change.
+ * packaging: sysconfig files no longer installed
+
+ libvirt used to provide defaults in various /etc/sysconfig/ files, such
+ as /etc/sysconfig/libvirtd. Since these files are owned by the admin, this
+ made it difficult to change built-in defaults in case such file was
+ modified by the admin. The built-in defaults are now part of the provided
+ systemd unit files, such as libvirtd.service. These unit files continue
+ to parse sysconfig files, in case they are created by the admin and filled
+ with the desired key=value pairs.
What do you think of the below, slightly reworded variant? I spent too much time
word-smithing and not sure if the result is any better :-).
+* **Packaging changes**
+
+ * sysconfig files no longer installed
+
+ libvirt has always installed service configuration files such as
+ /etc/sysconfig/libvirtd, and used these to provide various service
+ defaults. Since sysconfig files are owned by the local admin, changing
+ or adding built-in defaults is difficult when the files have been
+ modified by the local admin. The built-in defaults are now part of the
+ provided systemd unit files, such as libvirtd.service, and the sysconfig
+ file are no longer distributed and installed. The systemd unit files
+ continue to parse sysconfig files, in case they have been modified or
+ created by the local admim with site-specific settings.
Jim
