Re: Subversion transactions within post-commit

On 3 August 2011 04:37, David Weintraub <qazwart_at_gmail.com> wrote:
> NO! NO! NO! AUUUGGGHHH!
>
> Never update a repository with a hook.! That's why you're given the
> relatively safe "svnlook" command. It allows you to look, but not
> touch a repository.
> ...
> SNIP
> ...

Arrrgghhh damn it! Exactly what I feared. Especially the recursion. So
much so that now I think I was in denial all the while.

OK, looks like I have to explain a bit further to clear this up and
hopefully get some solutions.

We use the repository to directly serve some files (so Subversion
updates are immediately reflected). Something like
http://subversion.apache.org/faq.html#website-auto-update

So $files.subdomain.org/public_html is actually a local checkout of
$svn.subdomain.org/public_html/trunk/$somedir, and whenever someone
commits something to the SVN repo, the post-commit hook updates the
local checkout. So anyone browsing the file server will get the most
recent files.

However, we need to be a bit more personal than that. We need to do
some checks on those files and remove ones that should not be there.
We need to do this immediately after the commit, so cron is not an
option. How should we go about doing this?

--
GPG/PGP ID: 19BAA7AD