[bind10-dev] Updating configuration smoothly when options are removed

[Stephen Morris]

On 01/03/2012 09:52, Michal 'vorner' Vaner wrote:

> 
> • Have a configuration-only approach. Add a new data type for an
> option, and it would be „deprecated“. If an option would be
> deprecated, and found in the configuration, a warning would be
> produced, but the check would pass (no matter of the data type
> there). There could be a command to clear all the deprecated items
> from configuration, like „config purge“.

I prefer this option, I think it is less complicated for the user.

But why warn the user at all?  The option is not going to be used, it
has no effect on the code. Telling them that an option they may not
remember setting is now deprecated will only generate confusion.

Also, why have a purge command?  The software can be written so that
if a configuration update is made, redundant options are not written out.

(Of course, the drawback is that a user may never modify their
configuration file, so the list of deprecated options will continue to
get larger and larger.)

Stephen