Re: How to handle a config(noreplace) file that needs to be updated

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jan 3, 2021 at 3:01 PM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote:
>
> Dne 03. 01. 21 v 20:16 Robert-André Mauchin napsal(a):
> >
> > I have a project for which the config file (toml) has been significantly changed, notably renamed sections. As such some
> > older config parameters won't work anymore.
> > However the current config file can't be overwritten because of config(noreplace) directive. How do I recommend my users
> > to move to the new config format?
>
> 1) If their system is Ansible managed (should be), they simple deploy new config.
>
> 2) If they manage the system manualy then
>   rpmconf -a
> should be run after each (major) update.
>

Another option is to add a pretrans scriptlet to rename the file to
force the new config to be installed in place.




--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux