Re: Why does autogen.sh throw away the config cache?

On Mon, Sep 25, 2000 at 11:57:47AM -0500, Jim Blandy wrote:
>
> The following stuff in `autogen.sh' seems wrong to me.
>
> # toss our old config.cache. it may be invalid now.
> rm -f config.cache
>
> One needs to toss the cache when the results of tests have changed,
> not when the tests have changed. I haven't really noticed that that
> happens too often.
>
> What was the specific motivation for this?

I put that in there. It is possible that a change in the configure.in could
invalidate the contents of the cache, so it gets deleted to be safe.

For example, you might define a (cached) variable to be yes/no, but then
decide later that it should be 1/0. You edit configure.in and run
autogen.sh. That cache better be deleted or you're going to be scratching
your head for a while trying to figure out what is going wrong.

If you want to add an optional switch to autogen.sh to disable the deletion
(the default "should" be to delete the cache), then go for it.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/