Four questions

[Walter E. Brown]

I would appreciate insights and advice regarding the following:

1)  In a context where one configure script invokes another (via
AC_CONFIG_SUBDIRS), I've successfully used AC_CONFIG_AUX_DIR to have all
share a common repository of tools (e.g., install-sh).  I wonder whether
this can be extended to include, for example, other potential commonalities
such as aclocal.m4 and autom4te.cache/.  If so, what is the recommended
approach?  If not, what are (some of) the technical issues that would
prevent it?

2)  Is it possible to write configure.ac so that --config-cache is enabled
by default?  Again, how would this be best done?

3)  I read that it is recommended (for portability reasons) to avoid use of
filenames that contain more than one dot; however, I see that a file named
defs.h.in is being generated on my behalf.  Is there a way to avoid this
behavior?

4)  Finally, I wonder whether there is a recommended way to clean out, from
the source tree, all generated files (such as *.in).  This would, for
example, be in preparation for a CVS check-in in an environment that does
not bother keeping generated files in CVS.

Thank you.

        - WEB

--
Walter E. Brown, Ph.D.                        voice:  +1 630 840-2784
CEPA Department, Mail Station 234
Fermi National Accelerator Laboratory
Batavia, IL  60510-0500
USA