Re: cache directory is not removed

[Bill Wendling]

Also sprach Akim Demaille:
} >>>>> "Steven" == Steven G Johnson <address@hidden> writes:
} 
} Steven> Bill Wendling wrote:
} >> I concur. It is an annoyance. Having a flag (--remove-cache) as
} >> mentioned above would be very nice. Having the cache directory is
} >> fine, but keeping them there is a pain...
} 
} I don't think you realize the impact of using the cache here.  On the
} file utils, on my machine, it means that running automake, autoconf
} and autoheader is about 1min long.  Remove the cache, it's three
} minutes.  Touch all the Makefile.am, i.e., run automake for each
} Makefile.am, and you get 1 minute per Makefile.
} 
} So, although I find it stupid, I'm ok to provide some --remove-cache.
} But I'm definitely against making this the default.  I'm ok to rename
} it as .autom4te.cache too, if you find it so ugly.
} 
I don't think anyone was advocating removing the autom4te.cache
creation, and I'm sure that there are valid uses for it. Yes, I also find
the amount of time it takes for autoconf to finish annoying, but when
you're working in a CVS directory, it's annoying to have this directory
there...and when you go to do a release, you don't want that directory
there. It's extra work, is all. I don't care, I suppose, which is the
default. I'd just like a way to remove the cache automatically.

As I said in a different post, sometimes the configure is automatically
regenerated during a snapshot release, say. In those cases, it's extra
work to remove this directory.

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