Re: DJGPP-specific aspects of the GDB distribution

[Eli Zaretskii <eliz at delorie dot com>]

> I've been playing with gdb/config/fnchange.lst and I've how tweeked my
> local snapshot process so that it updates that file as part of building
> a release.  Having achieved that, I'm now not sure that its the best
> thing to do :-/  The problem is that it creates a similar problem to
> what I created with my initial md5 checksum file.  It will change every
> night.
> 
> I suspect its better to have the file contain:
> 
> 	src/gdb/ChangeLog-3.x src/gdb/ChangeLog.3-x
> 
> and have something else handle the problem of the tar archive name. 

That ``something else'' could be a trivial Sed script that is run when
you say "make dist" (or whatever you say when you tar the
distribution).  We will then need to rename fnchange.lst into
fnchange.template, say, and have fnchange.lst be a generated file.

> Perhaphs some sort of dos script (?) that did the work.

DOS script (a.k.a. batch file) won't help: the users need fnchange.lst
when they unpack the distribution, because DJTAR, the unpacking
utility that understands that file, cannot run scripts, it needs that
file submitted to it in the final form.

> I can easily
> set things up so that the script is tweeked to contain the current
> directory name.

If you agree to have a Sed script, I can submit a change that will
take the version from the configure script.