RE: Automate the version number

Hi Jon,

> And what happens after you check in another file? The $Rev$
> keyword is not touched in your version.h file.

No it isn't. The $Rev$ keyword reflects the revision in which that
particular file was last changed.

IMNSHO storing the current revision number of a repository inside a file in
the repository is for wimps (people who don't trust their own build
process). Forgive my harsh words, I don't want to start a religious war
here, but I don't like the idea.

We have a version file that contains our software release number (x.y.z)
which is edited manually and which is under revision control. The repository
revision number is only added at build time when a release is made.

For lack of better knowledge. I'm not convinced that a client side
pre-commit-hook can ensure that if you store $WCREV$+1 inside a file, the
revision number of the repoitory will actually be equal to $WCREV$+1 after
the commit. Will it really hold off the transaction so that no one can grab
this revision number from you?

You also have to ensure that every client has the client side hook
installed. Clients won't be able to commit, because the version.h file has
been bumped to the next revision and is always out of date locally even if
you are working on a totally different section of the software. It may work
for a one-person-one-repository project, but I predict this will get into
your way as soon as several people start to work on the project
simultaneously.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org