Right, but go back and read the thread . Since we can't make it conditional on records.config, doing it only in RecordsConfig.cc makes it impossible to properly implement the verification features that was requested in a different ticket (which is a great feature for good user experience).
So, we should keep records.config in sync with RecordsConfig.cc at all time. That was the whole point of this exercise.
Another option, which I'm sure you won't like, is to remove these configs from records.config. As you know, we don't have everything in there anyways. This would in fact be my personal preference until this feature is always enabled at build time, but I'm not going to argue over this endlessly.
So, lets just make records.config and RecordsConfig.cc always match up; if a configuration is in records.config, it must always exist in RecordsConfig.cc, with the same value.