Re: DJGPP-specific aspects of the GDB distribution

[Andrew Cagney <ac131313 at cygnus dot com>]

Eli Zaretskii wrote:
> 
> > 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.

It still leads to a file that gets rewritten each time a distribution is
created.  Remember the problem I had with the md5 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 was thinking more along the lines of the user first extracting that
batch file and then having that extract the archive.
The other option is to have the DOS rename file as something separate.

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

No need, I've one working already - just didnt like the look of the
consequences of including it.

	Andrew