The suggestion:
A flag to clearmake to force building (unconditional), but produce a new winkable config record only in case is doesn't match with any existing one. I.e. perform the build avoidance check after the build.
We are aware of the problems induced by using unconditional builds.
We however recently started using a new version of HP OpenView. We first installed it on one host only in our LAN, and soon decided to move it to a new vob. We did it by placing a unix soft link as /opt/OV, pointing to the new vob (we found that this would be enough to allow the parallel development of software using different versions, obviously not to run them in all hosts).
We didn't want to disrupt our past builds, nor to disturb on-going development, so that we didn't set up these links on all hosts at the same time.
We found that old builds did not record any of the OpenView files, since these ones used to be found out of the vobs. Thus mismatches were not detected, and the old DOs could be winked in!