Re: %config, %config(noreplace) and %post-install actions

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

 



On Thu, 2005-07-07 at 11:13 -0400, Adam Welch wrote:
> I like the semantics of %config and %config(noreplace).  However, I find
> that I'd often like to make small modifications to config files as part
> of post-installation, and not have these modifications trigger the
> .rpmsave or .rpmnew on the next upgrade.  You see, often the
> configuration modifications that I make in post-install are of the
> "localization" variety, rather than the "customization" variety.  I'd
> like the "localization" mods to not be reflected in the "changed-or-not"
> status of the package.  That is, I think that I'd like to munge the MD5
> of various config files as part of post-install, to account for
> localizations.

One recommendation would be to source a file where all the localisations
go, that file could be a %ghost %config(noreplace) and sourced by your
main config.  That way you have only one volatile file.

Many Fedora and RHEL init scripts use a file in /etc/sysconfig for this
(often unowned though).

Paul



[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux