Nico Kadel-Garcia wrote:
> So can *not touching someone else's config files*. If I've gone to the
> trouble of locally or manually editing a config file, I generally
> don't appreciate your package manually tweaking it inside your RPM
> %post scripts in an unpredictable fashion. Replace it, or don't, but
> don't get cutesy with it. This is the problem with authconfig: it
> overrides local tuning.
Well, if upstream breaks config file compatibility, there are only 3 things
the packager can do:
1. retain your config file unchanged. The application will no longer start
up until you fix the config file.
2. delete or move the config file. That loses all your settings.
3. try to fix the config file automatically (and keep a backup). That should
normally allow the application to start without losing your settings. It
may or may not be practical depending on how significant the changes are.
The previous replies suggested option 2, which is exactly "overriding local
tuning". I suggested option 3, which, if possible, is less destructive.
But of course, I would first of all blame the upstream application for not
providing a migration path for existing settings!
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
