-----BEGIN PGP SIGNED MESSAGE-----
On 05/02/2020 20.07, Hans-Peter Jansen wrote:
| Am Mittwoch, 5. Februar 2020, 19:33:48 CET schrieb Andrei
|> 05.02.2020 00:19, Thorsten Kukuk пишет:
|>> One of the main reasons for the try to make the update of
|>> configuration files more robust.
|> Before: user edits file in /etc. Package update installs new
|> version as .rpmnew. User misses important changes.
|> After: user copies file from /usr/etc into /etc. Package update
|> installs new version in /usr/etc. This version is ignored because
|> file in /etc exists. User misses important changes.
|> Where exactly is difference and advantage from end-user
| The idea in the long run is teaching apps to merge their config
| values, similar to what systemctl edit (without --full) does.
| /etc should only contain values, that deviate from system
| So far the theory.
So I change the defaults to suit my needs by dropping a file to /etc.
Months later, the defaults change again. How do I see what are the new
defaults, how do I notice that I have to change the file in /etc again?
Because now I simply do:
meld /etc/configfile /etc/configfile.rpmnew
and instantly I see what is new and I can decide to use it or not,
entry by entry.
Cheers / Saludos,
Carlos E. R.
(from 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org