#!/bin/sh

# POST-REVPROP-CHANGE HOOK
#
# The post-revprop-change hook is invoked after a revision property
# has been changed. Subversion runs this hook by invoking a program
# (script, executable, binary, etc.) named 'post-revprop-change'
# (for which this file is a template), with the following ordered
# arguments:
#
#   [1] REPOS-PATH   (the path to this repository)
#   [2] REV          (the revision that was tweaked)
#   [3] USER         (the username of the person tweaking the property)
#   [4] PROPNAME     (the property that was changed)
#
# Because the propchange has already completed and cannot be undone,
# the exit code of the hook program is ignored.  The hook program
# can use the 'svnlook' utility to help it examine the
# new property value.
#
# On a Unix system, the normal procedure is to have 'post-revprop-change'
# invoke other programs to do the real work, though it may do the
# work itself too.
#
# Note that 'post-revprop-change' must be executable by the user(s) who will
# invoke it (typically the user httpd runs as), and that user must
# have filesystem-level permission to access the repository.
#
# On a Windows system, you should name the hook program
# 'post-revprop-change.bat' or 'post-revprop-change.exe',
# but the basic idea is the same.
# 
# Here is an example hook script, for a Unix /bin/sh interpreter:

REPOS="$1"
REV="$2"
USER="$3"
PROPNAME="$4"

# ---- resync comment changes after pre-revprop-change

LOG=/var/log/svn/pre-revprop-change

# production Trac
TRAC_ENV=/path/to/your/trac/env

# For testing, use:
# TRAC_ENV=...

# Python settings
PYTHON_HOME=/opt/python-2.4.4

PATH=$PYTHON_HOME/bin:$PATH
export PATH
LD_LIBRARY_PATH=/opt/sqlite-3.3.8/lib:/opt/python-2.4.4/lib
export LD_LIBRARY_PATH

# ----

if [ "$PROPNAME" = "svn:log" -o "$PROPNAME" = "svn:author" ]
then
	trac-admin $TRAC_ENV resync $REV 2>> $LOG.err >> $LOG.log
fi