On 4/13/21 5:02 AM, Tim via users wrote:
On Mon, 2021-04-12 at 14:37 +0930, Tim via users wrote:
> What doesn't change, though, are user settings. Any program that
> stores its settings in your homespace is unaffected by RPM updates.
> Your configurations carry over. However, some applications change
> their configuration format over time, and when the application is
> run, it may update its own configuration files. It's similar with
> system configuration modifications you've made that are stored in
> /etc.
Supplemental info: Config files stored in /etc are similar in that
they're separate from the application, and unlikely to be removed by a
package install or removal, but there are other differences.
Most applications store per-user settings, and those files are in the
user's home space. Few applications have system-wide configurations
that are stored in /etc.
Applications don't always provide you with a way to modify
configuration files in /etc (e.g. you hand-edit configuration files for
Apache).
If you modify their /etc configuration files, your modifications are
supposed to stay in place if there's any application update. It'll add
a .rpmnew file with the latest version's default configuration file,
this is for you to manage any changes to your configuration files.
It's possible for an application upgrade to move your old /etc
configuration files into a .rpmsave file, as a back-up, and the new
update to be the default configuration file.
I do sometimes notice those during my weekly patching, but never really
paid attention to them. Now I know what those are.
Thank-you.