Actually locally I'm building now with autoconf 2.59, automake 1.8.2, and gettext 0.14.1.
There was a big hurdle to get over to get to automake 2.5x but since then the releases have been easy. I do this because there are fixes to autoconf and automake and gettext that I want to take advantage of when I build my package for release. Remember that these tools are only needed if you want to build from CVS; they're not necessary if you want to build a released version. I build autoconf, automake, and gettext myself and install them in a personal directory that I use just for GNU make; I don't try to upgrade my system versions of these tools. Personally I use stow to keep multiple versions available, but that's not really necessary for others since once I make a release that depends on a given version I won't go back. As for checking in configure etc., that's not something I want to do. First, it's just not right to check in products of the build. Second, I'm involved in the FVWM project as well and we had no _END_ of troubles when we were checking in these files: everyone would have different local versions of autoconf etc. and so those files would constantly being committed with changes that moved them back and forth in all kinds of silly ways. We stopped doing that and life has been much happier since. -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make
