Thanks for your input. This certainly could work, except that the configuration files that I package often cannot source a config file. Thus the need for a more involved approach, such as that suggested by Rodrigo Barbosa, which I had hoped could be avoided. Adam On Thu, 2005-07-07 at 11:36, Paul Nasrat wrote: > 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 > > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list
