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

[Michal 'vorner' Vaner]

Hello

On Thu, Mar 01, 2012 at 05:43:58PM +0000, Stephen Morris wrote:
> 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.

For two reasons. One, I don't want to delete part of the configuration without
the user agreeing, because the user might want to downgrade. They try out new
version, find it doesn't work because of a new shiny bug. So they return to the
previous version and it does not work either, because the new version screwed up
the configuration.

The other is, maybe the option had a reason for exist for the user and now is
configured differently. The user will need a way to migrate the option (maybe
there could be a description of why the option was deprecated and what is the
replacement).

With regards

-- 
~, sweet ~

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120302/8bd40da4/attachment.bin>