Thanks for your suggestion. However, I do need see how it could work unless the localizations could all be known in advance. The localizations that I perform cannot be known in advance. Adam On Thu, 2005-07-07 at 11:47, Jason Pyeron wrote: > What we do here is to put the config as a seperate rpm. > > you can then produce a rpm for each localization setup. > > If you really want to get fancy, you can have the main rpm select which > rpm to install in post config and install it. > > > On Thu, 7 Jul 2005, 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. > > > > Now, it seems to me having used RPM and monitored this list for some > > time, that even if this is possible it may violate the "spirit of RPM". > > My sense is that RPM gurus tend to advocate for minimal %post-install > > activity, so that RPMs are harder to break and are therefore more > > flexible, and more easily reused in contexts such as yum. > > > > I'd appreciate comments both on the immediate problem and/or if/how > > "solving" it would violate the "spirit of RPM." > > > > _______________________________________________ > > Rpm-list mailing list > > Rpm-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/rpm-list > >
