subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Reser <...@reser.org>
Subject Re: unversioned properties: size limitations?
Date Tue, 12 Aug 2014 18:49:39 GMT
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

> 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.

> 3. svnversion won't report anything on 'svn export'-ed sources.

Your properties won't be available either.  If you script the export then you
know what the revision you're exporting is and can determine the information by
simply doing `svn log --limit 1` on the same target (path and revision) as you
exported.  In order to make sure there are no changes between the export and
the log if you're not using a revision number you'll probably want to look up
the last changed revision using something like the log command given above and
then export that revision.

> All that would be handled if there were a way to modify a transaction being
> committed :)

As Branko has pointed out if you have a mixed revision working copy even your
solution doesn't work because you don't necessarily have a state that ever
existed in the repository.  svnversion exists partly to help resolve that
situation.

It's difficult to give advice beyond this because I have no idea what language
you're working in, what your build system looks like, what you're actually
shipping (source or binaries), etc...

As I urged you before, you'd be better off asking on this list for advice to
solve the problem you're trying to solve than asking about problems you're
having with the solutions.  This is not an uncommon problem people need to
solve.  It gets discussed periodically.  There are no perfect solutions.

See X-Y Problem:
http://mywiki.wooledge.org/XyProblem

Mime
View raw message