This is the mail archive of the autoconf@gnu.org mailing list for the Autoconf project. See the Autoconf home page for more information.
Greg Woods wrote: > Just for the record, here's my scheme, including notes about how to > generate a release in an auto* package. This scheme has worked very > well in practice with several small tools and one fairly major package. > [...] > aclocal > autoheader > automake --gnu --add-missing > autoconf For a standard installation of autoconf and automake, shouldn't this be aclocal autoheader autoconf automake --gnu --add-missing ? With the other ordering you can create distributions with missing files because automake doesn't include some of the files which autoconf generates. > In order to build releases you *MUST* be using a version of GNU Automake > that includes support for proper CVS-based release management using the > 'make dist' approach. Out of interest, how does your CVS release management differ from that built into automake? Is it mainly a question of using `cvs export' to build the distribution subdirectory instead of copying files into it? How does it compare with doing a `cvs export', then configure; make; make dist in the exported directory? -Mark