You should be able to do the same thing in Perl or Python -- especially if
you use the API.

Of course, nothing says you have to use "svnlook" when you're looking at an
actual revision instead of just the current commit transaction. You can use
the "svn" command which has many more options and parameters. What you
cannot do is use "svn" with a workspace (you don't have one, and you don't
want to create one). But, as long as the arguments are with the Subversion
URL, you're fine.

With the standard "svn" command, you can get the previous changed revision,
and then from that, get the changed revision before that one. For example,
to get the first changed revision, use "svn info" without the revision
parameter:

*$ svn info http://subversion/dev/modules/foo/trunk/build.xml
*
*
*Then subtract one from that revision number, and put it into the next "svn
info" command. Let's say the above said the last changed revision for
build.xml was revision 60,000. I can do the same command for revision 59,999
and see what was the last changed revision before revision 60,000:

> In a post_commit hook, 'svnlook history' can be used to dig up details
> on the previous checkin of the affected file(s).
>
> Running
>
> svnlook history -r txn repo path
>
> returns a list of N historical entries of which the 2nd one is the repo
> on the previous repo version of the same file.
>
> Questions:
>
> a) Is this the best way of obtaining the first repo revision containing
> the previous version of the file?
>
> b) Is there a way to limit the output to a small number of entries? Some
> files have histories of several thousand entries, most of which aren't
> needed in this case.
>
> Any help appreciated!
>
> -- Mike
>
> Mike Schilli
> m_at_perlmeister.com
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2403903>
> To unsubscribe from this discussion, e-mail: [
> users-unsubscribe_at_subversion.tigris.org].
>