Handling mandatory config file updates

[Nils Philippsen]

On Thu, 2005-09-29 at 09:31 -0500, Jason L Tibbitts III wrote:
> I maintain a package (denyhosts) for which I would like to push an
> update.  Unfortunately the new version requires changes to the
> configuration file.  The syntax hasn't changed, but one setting was
> renamed and several mandatory ones have been added.  If the changes
> aren't made, the daemon won't start properly.
> 
> So, do I:
> 
> 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?

Nils
-- 
     Nils Philippsen    /    Red Hat    /    nphilipp at redhat.com
"They that can give up essential liberty to obtain a little temporary
 safety deserve neither liberty nor safety."     -- B. Franklin, 1759
 PGP fingerprint:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011