Version numbers

[Joseph S. Myers]

On Sat, 17 Feb 2001, Fergus Henderson wrote:

> I'm not so sure that this is a good idea.  Doing it this way would
> mean that adding a new front-end can't be done by just providing new
> files in a new directory.  Instead, patches to the language-independent
> stuff would be required.  Furthermore, such patches are very likely to
> have conflicts.  That could be a real pain.

It would be possible to have a separate file for each front end needing
one, provided that the main file points to all the others as possibly
needing updating when new releases are created.

[ Should the g77 version change on the mainline to 0.5.27? ]

As is, the changes to 3.0 on the release branch are not complete, since
gcc.texi and f/root.texi contain references to the old 2.97 version
number.

I'd suggest something like the following (except that I don't think gcov
and CHILL need their own versions):

gcc/versions:
# Master list of versions for GCC.  All other references to versions in
# GCC should be derived from this at configure or make time.
# See also: f/versions for the G77 version, ch/versions for the CHILL
# version.
gcc_version=3.0
gcc_date=20010217
gcc_status=prerelease
gcov_version=1.5

ch/versions:
version=1.5.2

f/versions:
version=0.5.26

-- 
Joseph S. Myers
jsm28@cam.ac.uk