Re: howto? specify non-mergability for a file

On Fri, 30 Sep 2005 09:17:18 +0200, Unspammable
<unspammable@gmail.com> wrote:

>The build number indicates (roughly) how many times the project was built,
>and is somewhat useful as such.
>If it's not under source control the number would be a very poor indicator.

Surely it's a very poor indicator anyway. Even if you could take the
newest (timestamp) file (which you can't, BTW), it doesn't give an
indication of how many times the project was built.

1. User A checks out the project, revision = 1234, build number = 5.
2. User B checks out the project, revision = 1234, build number = 5.
3. User B builds the project, build number = 6.
...
9. User B builds the project, build number = 12.
10. User A builds the project, build number = 6

The 'User A' version of the file has the more recent timestamp, but in
fact the project has been built 8 additional times since it was
checked out, not the once the build number would indicate.

>The file containing the build number must be
>updated before the build takes place. The revision number is updated when
>the file is commited, correct?

Yes.

>This will create a discrepancy between the
>revision number and the version string attached to the executable.

Not necessarily. Either
(a) commit the file containing the revision before building the
executable, or
(b) use svnversion in your build scripts (see the FAQ) to populate
version string.

Greg

-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org