Re: config.in

[storm@cua.dk (Kim F. Storm)]

Andreas Schwab <schwab@suse.de> writes:

> Richard Stallman <rms@gnu.org> 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 :-)

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)
files are in CVS, why they are there, and what the dependencies
between all those files are.

Of course, it should also mention "make bootstrap" :-)

And it would be nice if it briefly described the steps normally taken
to build and release a new distribution (e.g. what to put into
ChangeLog, what files to update afterwards [with version info] etc.)


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk