Hello, Harlan!
> Sometimes I change the logic in configure.in and discover that my cached
> values are overriding my new logic.
When I change the logic I remove all the lines from the cache that may
have any influence on the changed piece.
E.g. if I modify a test for libfoo I delete the entries for libfoo, foo.h,
sys/foo.h and so on to be on the safe side. But I still gain a significant
speedup due to the cache values for unrelated things.
> This also bites both other developers as well as users who track
> distributions via CVS instead of tarballs.
When I track distributions via CVS I delete much more than just
config.cache. I save local patches to a separate directory and bring the
repository to the pristine state before running "cvs update"
This saves me many problems that the users will never have anyway and
makes it easier to discover real problems early.
> I'd almost like to see a "version" number in the cache, which I can "bump"
> whenever I make a "significant" change to the logic which has the effect
> of...
rm config.cache
is easier and friendlier to CVS IMHO.
Pavel
