Hi Steffen, > Then `configure' only needs to change when something changes, like > adding perl(1) detection or similar.
It can also change due to different versions of autoconf being used by developers; the same functionality represented by differing expansions of the macros. Alternating commits by two developers then cause a back and forth change to keep being checked in unless they make an effort to commit `what's changed but not configure', and that relies on them not making a mistake and forgetting that configure has a functional change just this time. Cheers, Ralph.
