Re: [rfc] Move Makefile.in:VERSION to VERSION file

[Andrew Cagney <ac131313 at cygnus dot com>]

Eli Zaretskii wrote:

Did I reply?

> > The intention is that a nightly (1) cronjob would update the VERSION
> > number with the new days date.  Each update would involve a CVS commit.
> > If the VERSION is sitting in a file like Makefile.in (or to a lesser
> > extent version.c) that file's CVS log will slowly drown in those CVS
> > commits.
> 
> How about using an include directive in the Makefile, so that the
> actual variable assignment could be on a separate file?  Or you could
> say something like "VERSION=`cat VERSION`", with a similar effect.
> These both will work with DJGPP.

The generation script would still need a dependency on ``VERSION'' since
a cvs update will most likely bring in an updated version number.

> > By creating a separate file that contains just the version number that
> > problem can be avoided.  It makes the update process really easy and
> > insulates the crontjob from any changes to how version.c is created.
> 
> Yet another idea is to have the cron job create version.c directly.
> After all, it's not much larger than VERSION.

Yes, I thought about that.  I'd just like to keep the script as simple
as possible.

> Actually, it _can_ be upper-case, just not all of it.  VERSION.in or
> VERSION.txt should work, for example.

Ok if I just go with ``version''?

	Andrew