On 25 Mar 2021, Weatherby,Gerard wrote:
svn-backup-dumps.py is a pretty nice script, but it took way to
look
for me to figure how to put in a post-commit script. Attached is
example.
Thanks for this contribution. It seems good to provide this
example post-commit script, but instead of providing it as a
separate file, what if it were just shown in the relevant part of
the long-comment documentation in
'tools/server-side/svn-backup-dumps.py'? I'm thinking of the
section that starts:
# 3. Create incremental single revision dumps (for use in
post-commit).
IMHO that would be better than putting a new file in
tools/server-side/, especially when that new file has a
subordinate relationship to an existing file there but that
relationship is not immediately obvious from just looking at the
directory.
Thoughts?
Best regards,
-Karl
[[[
Provide example post-commit for svn-backup-dumps.py
]]]
Index: tools/server-side/svn-backup-dumps-post-commit
===================================================================
--- tools/server-side/svn-backup-dumps-post-commit
(nonexistent)
+++ tools/server-side/svn-backup-dumps-post-commit (working
copy)
@@ -0,0 +1,6 @@
+#!/bin/bash
+#
+# Sample linux post-commit script for svn-backup-dumps.py.
+# Logs to system log
+#
+(/usr/bin/python3 /usr/local/bin/svn-backup-dumps.py -r "$2" "$1"
/wekasubversion/incremental) |logger
