[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: config.in

From: Kim F. Storm
Subject: Re: config.in
Date: 19 Apr 2002 15:02:21 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.50

Andreas Schwab <address@hidden> writes:

> address@hidden (Kim F. Storm) writes:
> |> Andreas Schwab <address@hidden> writes:
> |> 
> |> > Richard Stallman <address@hidden> writes:
> |> > 
> |> > |> Things may be different now with src/config.in.  There now seems to be
> |> > |> a Make rule to update that file, so it might try to run automatically.
> |> > |> This is no good.
> |> > 
> |> > There was always a rule for configure as well, otherwise I wouldn't have
> |> > added one for config.in.  But the difference with config.in is that it
> |> > depends on a third file, src/stamp-h.in, that functions as a timestamp
> |> > file, because autoheader does not modify its output if it wouldn't 
> change,
> |> > thus to avoid running autoheader again and again the stamp file is 
> needed.
> |> > I have already extended make-dist to fix the timestamps for distribution.
> |> 
> |> I think I got lost half way through those changes....  I don't think
> |> I'll ever dare adding a new parameter to config.in or configure :-)
> You will not ever need to modify config.in any more.
> |> May I suggest that you write a short INTRO_CVS file (not to be
> |> included in a dist) which explains what tools are needed to
> |> reconfigure things (autoconf version etc.), what (config related)
> Just use autoconf >= 2.51, as stated in configure.in (AC_PREREQ).
> |> files are in CVS, why they are there, and what the dependencies
> |> between all those files are.
> In addition to autoconf you just need to run autoheader to update
> src/config.in.  That's all.

Ok, I can understand that....  But it would still be nice if we
documented it (for the sake of future emacs hackers and old-timers
like myself with flaky memory) and stated our policies regarding which
auto-generated files still need to be checked into CVS (e.g. config.in
is there, *.elc is not).

The file could also state how to become a developer (who to contact to
get write access), release policies, and other policies.

And the use of "make bootstrap" of course :-)

Just start small and simple -- we can enhance it on the way ...

Kim F. Storm <address@hidden> http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]