On Tuesday, June 4, 2019 12:23:56 PM CEST Johannes Meixner wrote:
I do not see how the actual issue could be solved
by storing config files at a different location.
As I can see there is a improvement. The goal is separate the default
configuration file (provided by the RPM, that maybe is a direct reflect of the
one that the developer provides) from the changes that the user have locally
in the machine.
If you have a mechanism where you can load the default configuration file and
add on top of it the changes that the user provide, you will be more resilient
and safe to changes.
For one you will not have .rpmnew or .rpmsave that you need to check and
And for other, if a new option is provided and the RPM config file have a
sensible default value written for it, this will be accounted the next time
the service restart. Only this, IMHO, makes the effort worth it.
SUSE Linux GmbH
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org