On Tuesday, August 12, 2014 11:49:39 am Ben Reser wrote: > I intended to reply to your other thread given roughly the same svnversion > advice that Branko has already given you. > > On 8/12/14 9:09 AM, Alexey Neyman wrote: > > 1. svnversion reports the revision of the check-out, not the revision of > > the last modification. > > Use one of the alternatives that behaves the way you want. To save > retyping info I've already provided elsewhere see this: > https://stackoverflow.com/questions/21447373/how-to-get-correct-svn-version > -number-on-unix/21448972#21448972 > > For reference SubWCRev is something that comes with TortoiseSVN: > http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-subwcrev.html
Actually, it's even easier than that. I somehow missed the -c option to svnversion. > > 2. svnversion does not provide the $Date$ information. > > Patches welcome as always. If you don't want to write the patch you can > always ask for it. I think I can write such patch myself :) > > 3. svnversion won't report anything on 'svn export'-ed sources. > > Your properties won't be available either. Properties won't, but expanded keywords will be present in 'svn export'. $Revision$ will change in response to a property change. Please consider these questions closed. For the 'last changed rev/date' I'll modify the 'svnversion -c' and will submit a patch to support reporting the dates as well (hopefully, it can then be applied to 1.8.x branch as well) and for the caching the results of file analysis, I'll use a post-commit script (since not performing that action does not compromise the integrity of the project in the repository). Regards. Alexey.
