matt massie wrote:
guys-
let's talk.
if( you know about autoconf, automake and libtool)
goto QUESTION:
If only I could forget...
QUESTION:
should i remove all the autoconf, automake, libtool derived files and
require that we run...
# aclocal
# autoheader
# automake
# autoconf
before we run
# ./configure
on the CVS source?????
I'm fine with this. Having a specific set of these tools installed isn't a
problem for me.
disadvantage: if we are using different versions of the auto* tools then
we'll be assuming things work on a particular platform when they may not.
also, people who download the CVS tarball will have to do the same thing.
We can always check in a README.CVSusers file naming the "blessed" dev
versions.
for example, when we create a release, we may be using a newer/older
version to create the derived files. bad.
As long as the versions we use are publicized in the documentation
somewhere, this shouldn't be an issue. People compiling source should be
familiar with the "if it breaks, RTFM" process... and if they're not, think
of what a valuable lesson they're learning!
i'm running...
autoconf (GNU Autoconf) 2.53
automake (GNU automake) 1.6.3
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52)
Through trial and error I'm basically using the same versions... :)
