Simon Large wrote:
>> Eg. replace "$WCREV$" with "$WCREV: 504 $" inside the files instead of
>> requiring both source and destination files?
>
> Because these are not svn:keywords, and they are used differently. Take
> a look at the nightly build scripts to see how the version numbers are
> created. Would you prefer to see "V1.1.5.2980" or "V1.1.5.$WCREV:
> 2980$"?
Thanks for explaining, you're right.
I come from a VS.Net / NetBeans etc. world where builds are done with
the click of a button in the GUI, and SubWCRev doesn't lend itself to
this way of working very easily. The Subversion way of doing keywords
work better there.
>> Also applicable for the complex attributes you've just crafted:
>> "$WCMIXED?TrueText:FalseText$" becomes "$WCMIXED?TrueText:FalseText:
>> TrueText $.
>>
>> In this regard, the colon that you've chosen between TrueText and
>> FalseText is IMHO very unfortunate, and should be replaced with
>> something else quickly, before it becomes common usage, so that we in
>> the future can be compatible with the CVS/SVN way of doing keywords..
>
> Same applies here. We use these also in the doc files to put a readable
> string in the CHM and PDF files. Again, we want pure text, without
> $WCxxx.
Ok, thanks for explaining. Wrong context though, I think. It applies
for the previous paragraph ("also applicable..."), but it doesn't
apply for changing the colon to something else, just in case.
I still think the colon should be changed :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 9 19:48:07 2005