On 04/06/2019 19:53, Johannes Meixner wrote:
Hello,
I do not see how the actual issue could be solved by storing config files at a different location.
I think the actual issue is the conflict between what the admin wants to have in his config files versus what a Linux distributor wants to have in his config files.
It can pretty easily because under this system the version stored in /etc by the system administrator only contains the values the administrator wants to change from defaults (in theory anyway), then the logic is simple for the program if a config value exists in /etc its the one the program should use, meanwhile its easy for the developers to change the defaults to whatever or add / remove new ones without adding any files, this aproach can still sometimes have the occasional issue for example the administrator could choose a default for a security cypher that becomes insecure and is blocked upstream, at this point the new version of the program has to fail on its next start and leave a nice message in the logs for the administrator to fix, of course a Micro OS system might notice the service not running and roll back to the previous version and the admin might not notice but thats a different problem to solve. But in general it seems better then attempting to merge 2 full config files everytime. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org