From: Godmar Back (gback@cs.utah.edu)
Date: Mon Jan 25 1999 - 19:32:25 EST
>
> I feel equally unhappy that a build can change the source - I consider the
> source to be read-only and the build process shouldn't muck with it.
>
To give Alexandre some credit here, this should no longer happen
(and in fact hasn't happen for me for a while now) unless you specify
--enable-maintainer-mode when configuring --- which I don't.
If you do have to update the .in files, what I do is to follow the FAQ
and perform a "aclocal; automake; autoconf; autoheader -l config"
in the top source directory.
Admittedly, this is very fragile with regard to the required versions
of the tool---I'm at a distinct advantage here
because I can do a:
set path = (~oliva/bin $path)
before doing it and get exactly the auto* versions you need.
However, there will still be conflicts if you do that which can result
from different people using different tools. For instance, the
CVS configure that was checked in used to be created by
autoconf 2.13, but I used 2.14. This is actually a problem somewhat
unrelated to automake/libtool --- you have the same problem even when
simply using autoconf. Purist may argue that configure should not be
in the CVS tree, but I think we can live with it for now.
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:48 EDT