Ralf Wildenhues wrote: > would you mind a list of URLs pointing to general CVS > instructions rather than a web interface? Usually the latter is only a > couple of clicks away from the former, but the other way is difficult to > find.
Might make sense if you're interested in different things than I am. I was only interested to see "How do they use gnulib-tool" and "Which modules do they use". > If made accessible in an automatic way, one could even (gasp!) think > about some semi-automatic testing of the packages (or at least those > of them that do not have excessive prerequisite lists) ... Hmm, since some packages are not checking into CVS the autocopied files and not all have an 'autogen.sh' script, it might be easier to take the complete tarballs as a starting point. Just tried this: $ wget ftp://ftp.gnu.org/gnu/bison/bison-2.3.tar.gz $ tar xvfz bison-2.3.tar.gz $ cd bison-2.3 $ $GNULIB_TOOL --update but, alas, it doesn't work because gnulib-cache.m4 is not distributed (that's because automake now distributes only those .m4 files from the m4 directories that don't have a Makefile.am that are actually used by configure.ac, and gnulib-cache.m4 isn't). I think gnulib-tool should be changed so that gnulib-cache.m4 is always distributed. Objections? Bruno
