Re: A better autogen.sh

[Eli Zaretskii]

> Date: Wed, 16 Mar 2011 02:23:09 -0700
> From: Paul Eggert <address@hidden>
> CC: Glenn Morris <address@hidden>, address@hidden
> 
> On 03/16/2011 01:47 AM, Eli Zaretskii wrote:
> > The trouble is, we keep requiring newer versions of autoconf from time
> > to time, and later more frequently than in the past.  Experience shows
> > that upgrading autoconf on fencepost involves asking GNU sysadmins to
> > do that, which takes a non-trivial amount of time and sometimes
> > repeated pinging.
> 
> That may have been a problem in the past, but it's not a problem now,
> because fencepost's /usr/bin/autoconf is Autoconf 2.65, which
> is good enough for Emacs.
> 
> In the long run I don't expect this to be a major issue,
> but if I'm wrong, I can volunteer to keep
> good-enough versions of automake and autoconf installed on
> fencepost, under ~eggert/bin say, and that will be enough to
> get it to work.

Thanks, but I don't think it is practical to make the maintenance of
non-Posix platform depend on people who are not interested in Emacs
running on those platforms.

Could you please instead tell if new and modified #define's in
config.in can be detected by grepping certain files for AC_DEFINE or
similar directives, and which files to grep?

If it is possible to specify which files to grep for what patterns,
that would open a way for a practical maintenance routine of config.in
outside the main directories of the Emacs tree, and we could then put
this issue to rest (until the next time, which will doubtlessly come).