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

Re: determining what was updated, using client hook scripts

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Mon, 4 Nov 2013 14:46:24 -0500

On Mon, Nov 4, 2013 at 1:23 PM, Alexander Haley <ahaley_at_meditech.com> wrote:

>
> I wish the POST-UPDATE client hook received (as an argument) a file
> containing the explicit list of paths/files updated.
>
> For my build environment's needs I need a list of which files were updated
> when a client has updated the working copy. I currently achieve this by
> the following inefficient technique.
>
> First) ... now I have a before and after set and from these I subtract
> and decipher exactly which files where updated.
>
> Why not use the timestamps of the files? Unless you have SVN configured to
set the timestamps to the last modified time (as of the commit) the files
just updated will have the most recent timestamp.

FYI, my team uses GNU Make to perform the actual builds. Make automatically
detects changed source files by comparing the timestamps of the source
files to the timestamps of the built files. Make is not limited to building
executable files, it can be configured to build, for example, documentation
or even websites. Make can run any tool that can be run from a .BAT script.

If you really need a text file with a list of changed files, rules like the
following will do that:

sources := $(wildcard *.cpp)
changemarks := $(sources:.cpp=.changed)

.SUFFIXES: .changed

changes.txt: $(changemarks)
    del $@
    rename changelist $@

.cpp.changed:
    echo $< >>changelist
    touch $@

Windows executables for GNU Make (and other GNU tools) are available at
*gnu*win32.sourceforge.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3067854

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-11-04 20:46:48 CET

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.