[developers] *cvs-version*

[Ann Copestake]

probably mostly to oe -

How is the LKB *cvs-version* currently being set?  What's the policy?  Some
time ago, the message that used to appear when one checked in code about
remembering to update the version number ceased to appear and I've not just
forgotten to do it, but forgotten how to do it ...  Actually to the extent I
thought about it at all, I assumed it was being updated automatically when new
code was checked in.  Obviously it isn't - from the log, it looks as though
it's recently only being updated via `auto-update for build'.  The reason for
asking was that I noted that in the current ERG script, there is an inadequate
test for the lkb version via looking for a global variable.  The test will
still be true for the current version, even though we would now like it to be
false.  I was going to write a utility that parsed *cvs-version* and allowed
people to specify dates and date ranges, but if *cvs-version* isn't getting
updated, that's not going to be helpful.  For most people, the version
constructed at build will be OK, but not if people are updating from CVS
sources.

Ann