-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 2/13/2008 3:36 PM: | Hello, | | is it worthwhile to generate m4/tests/testsuite from within bootstrap, | so that then, | ./configure && make all install | | does not need the autotools?
Sounds like a good argument to me - allowing you to run bootstrap on a git checkout on a full-fledged machine, then copy the directory structure over to a punier machine to see how things fare. However, looking at history: http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=be70d90 there was a point in time where half of the testsuite was generated at bootstrap (but not the part that required autom4te). So this would be a change in the opposite direction. I'm also worried about timestamps; one of the tests makes sure __m4_version__ outputs the same thing as what configure.ac uses, and I still haven't gotten git-version-gen working nicely with m4. I'll play with the idea some, but it's too early to tell whether I'll commit a patch along these lines. Fortunately, 'make dist' makes sure the testsuite is up-to-date, so a snapshot tarball does not need autotools to be tested. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHs5K184KuGfSFAYARAhXyAJ0Zgc5DGiuDy8PPv8+0QvtAvSbxNgCgpUCe BoyhyojOVH5gI8fmbfuHr+M= =OjNo -----END PGP SIGNATURE----- _______________________________________________ Bug-m4 mailing list Bug-m4@gnu.org http://lists.gnu.org/mailman/listinfo/bug-m4
