On Thu, 2005-09-29 at 17:32 +0200, Nils Philippsen wrote: > On Thu, 2005-09-29 at 09:31 -0500, Jason L Tibbitts III wrote: > > > > 1) Tag a fresh config file as %config instead of %config(noreplace) so > > that the updated package will at least start but will require > > operator intervention to return to previous behavior. (Assuming > > the admin notices the change in behavior.) > > > > 2) Attempt to fix up the configuration in %post and hope I don't > > mangle something. > > > > 3) Do nothing and hope the admin notices the error messages when the > > daemon restarts. > > 4) Build new package only in devel and mention the change in FC5 release > notes? Personally, I'd go for 1) and 4) and whine upstream, asking them to take backwards compatibility issues better into account between releases. Also, dunno if there will be release notes for FE.
