[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:keywords settings make file different?

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Fri, 13 Aug 2010 07:35:58 +0200


On 13 August 2010 04:07, Edwin <edwintai_at_gmail.com> wrote:
> I use 3party's Lib and it works okay before I set svn:keywords on it.
> Lib should be a binary file,I think if it replace keywords in binary
> would break the file.

Yes it would, as the svn:keywords processing assumes that you are
using it on files that can grow/shrink in size at will. Binary files
usually cannot (as they contain internal pointers/data structures that
are 'fixed').

Be sure to only apply the svn:keywords property to files that can be
modified without breaking.

There is a way to make sure the space used by the svn:keywords is of a
fixed size, but you need to prepare the file before you apply the
svn:keywords property. Please verify in the manual[2] how to do this.
Caveat: if the binary file is a 'compiled' version of some source
file(s) and if it includes the original source code lines, the the
svn:keywords from the original sources may also be present in the
binary file; depending on the tools being used, there may not be a
guarantee that these texts are kept 100% intact (compression,
whitespace trimming etc. could potentially break the 'svn:keywords
using fixed amount of space' solution.

[1] - http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html#tsvn-dug-propertypage-props
[2] - http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.keywords.html

.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-13 07:36:06 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.