>>>>> "Sam" == Sam Steingold <[EMAIL PROTECTED]> writes:
Sam> nope. when I distribute CLISP, I cannot assume that my users Sam> have autoconf, so I distribute the generated configure scripts Sam> too. i.e., the configure scripts are in the source tree and are Sam> regenerated just before a release. thus, if I use autoconf 2.53, Sam> I have to remove the cache directories by hand before a release, Sam> so that they do not end up in the distribution file. But how do you write you dist target? How come it ends in the tarball!?! Sam> this is a major inconvenience. Sam> adding a --remove-cache option To who? Automake + autoconf + autoheader + autoscan + autoreconf + autom4te + autoupdate ? Sam> (or --no-cache - for not creating the cache in the first place) Sam> is not too much work, and I can submit the patch if you wish. It is much work. For a start, if you remove the cache, there is no longer autoheader. Or autoheader first write the cache, then reads it, and finally removes it? Sam> please note, that I am not your only user who is unhappy with the Sam> cache directory. This is because we created it *before* you can notice how useful it is. Had we made it backwards, we'd be drown under complaints.
