Stopping daily bump of version.c on old/closed branches

[Gabriel Dos Reis]

Daniel Berlin <dberlin@dberlin.org> writes:

| On Wednesday, April 23, 2003, at 02:41  AM, Gabriel Dos Reis wrote:
| 
| >
| > Hi,
| >
| >   As I announced earlier, the branch gcc-3_2-branch will be closed
| > after GCC-3.2.3 is realesed.  By that I really mean that we don't have
| > anything like GCC-3.2.4 floating around.  My inclination is to have
| > the conjob that currently bumps gcc/version.c not touch gcc-3_2-branch.
| >
| What is this script written in?

sh.

| For that matter, what are most of these scripts written in?
| If it's perl, we really should just keep a simple (tab or comma)
| delimited flat file (or mysql, though i think that's overkill)
| database.
| that has the current branches, and a description of each, and have
| these scripts pull from it.
| You could also make the web page pull the descriptions from the db,
| too, be it on the fly or once a day.
| It seems every time someone adds or obsoletes a branch,  there are
| 50 places that need to be updated, rather than 1.

strongly agreed with your suggestion.

| If these scripts are in perl or python, i'll happily volunteer to make
| them do this.
| My awk/sed/sh foo just ain't good enough, however, and i'm actually
| proud of that.
| :)

:-)  
Thanks for the prompt answer.

After I raised the issue with Gerald, he was kind enough to do my
homework and pointed out that the actual script is taken from:

    egcs/maintainer-scripts/update_version

The bits that are of interest are:

    # Compute the branches which we should update.
    $CVS co gcc/ChangeLog
    BRANCHES=`$CVS status -v gcc/ChangeLog \
              | awk '{print $1;}' \
              | egrep 'gcc-[0-9]+_[0-9]+-branch$'`
    # Always update the mainline.
    BRANCHES="${BRANCHES} HEAD"

Indeed we could just use a plain ascii file as db for active branches names.


My first question would be:  Do people think that we should stop
updating gcc/version.c on old or obsoleted branches?

-- Gaby