Re: cache directory is not removed

[Bill Wendling]

Also sprach Earnie Boyd:
} 
} There is an easy way to get rid of the cache directory.  It involves a
} simple command.  This commands  repeated use will not even come close to
} the amount of bits spread for this thread and others like it.  Just `rm
} -rf autom4te-2.53.cache' if you don't want it laying around.
} 
That's all fine and good, but we automagically regenerate our configure
files when we do a snapshot of the code (to change the version number in
them). It complicates things unnecessarily.

BTW, the removal of automatically generating a config.cache file by
default was a bad idea, in my opinion. We actually use that file quite a
bit. There are a lot of machines which take a long time to run configure
on. If you have to reconfigure for some reason (to turn on another
option, say) it's very nice to have that file there. In fact, for some of
those machines, we copied information from the config.cache file and load
that into the configure script so that it will skip those test (in
particular, tests which determine the size of various types).

Why was config.cache deemed removable but the autom4te.cache directory
isn't?

Very strange...

-- 
|| Bill Wendling                        address@hidden
|| Coding Simian