On Tuesday 2019-06-04 09:43, Carlos E. R. wrote:
The goal is to provide a concept working for all Linux Distributors (like
the FHS, preferred is to get this into the FHS). Short to midterm, it should
solve the problems with atomic updates. Midterm to longterm, the result
should be, that no package installs anything in /etc, it should only contain
changes made by the system administrator or configuration files managed by
the system administrator.
But this makes harder to read the actual configuration, because we then
need to read two files: the one put by rpm, and the one we modified.
There are two types of programs (and hence config strategies) to be aware of.
1. "Regular programs". Picking mc as my example.
Such programs have built-in defaults and generally only need to read "one
file", or more specifically *one kind of file*, namely, the *user preferences*
that override parts of the defaults.
2. "Cooperative duos". Picking systemd as my example:
systemd itself cannot offer defaults to start arbitrary programs, because
arbitrary programs live at arbitrary paths; it has to rely on another package
providing additional information.
Consequently, systemd needs to read *two kinds* of files, namely the *vendor
snippet* from /usr/lib/systemd/system/, and the *user preference snippet* from
Now, regular programs outnumber cooperative duos, so the config file problem is
not nearly as big as some make it out to be.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org