Ah, indeed. That would work, though it seems a blunt tool. Maybe I'd use %ghost's in the RPM that deploys the configuration, then have the localizing RPM built in-situ own the configs. Hmmm, it seems like this would benefit from the creation of a generic framework to do exactly this kind of thing (rpmify-dynamic-configs-1.0.rpm), since I have a number of RPMs that would benefit from the approach. Again, thanks for the input, though I will continue to hope that a less involved way (I didn't say easier) will be suggested. Adam On Thu, 2005-07-07 at 12:19, Jason Pyeron wrote: > This is where we would build an rpm as part of post config. > > We have done some very complicated things, and the only problem we have > ever encountered was replacing in use files on cygwin. > > On Thu, 7 Jul 2005, Adam Welch wrote: > > > 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. > >
