Basically what you are doing is what is suggested:
http://subversion.tigris.org/faq.html#version-value-in-source
But, you are better of using build numbers in your files and then
tagging with build numbers. How could you possible know what revisions
the file will be committed to? You could do an update which will tell
you that the current HEAD revision is say 1000 so you put 1001 into your
file. But, in the mean time someone else could have committed to the
repository hence making your actually commit be revision 1002.
BOb
> -----Original Message-----
> From: howszat [mailto:cgu0sij02_at_sneakemail.com]
> Sent: Tuesday, December 30, 2008 12:00 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Revision Number into a Binary file
>
> Hi,
> I would like to place the revision number of a binary file into
> itself. Doing this assures that the file can always be traced back to
> its source in svn. Is this possible?
> I have looked at subwcrev.exe but would like something a bit
> different. I would imagine it could be done with a pre-commit hook
> which looks up the next revision number and modifies the file. Has
> this sort of thing been done before?
>
> ------------------------------------------------------
>
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessage
Id
> =995482
>
> To unsubscribe from this discussion, e-mail: [users-
> unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=996083
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2008-12-30 17:49:27 CET