Re: version control of 'hooks' directory

Brandt, Servatius wrote:

> This is what I'm doing, too. Last week, when I searched the mail
> archive for a method how to put the hook scripts under version control,
> I found a tip by Mike Pilato, who suggested to add the 'svn update' to
> the post-commit hook. Then committing from the test repository means
> you get the live hooks automatically. It is also possible to put the
> files in the conf directory under version control.

I have used this approach (svn update in post-commit) for more than a
year now, and it works just fine. I have the hooks in the same repo as
they run on though.

Usually I test commits to the path checked out in the hooks dir by
running on a (cut-down) copy of the database before I commit them.

I checkout the hooks directory using file:// to the repo, so if I really
need to mock around with them "live", I can just stop the server and
edit directly on the checked out copy, do tests and then commit the
fixed version. I have only done this once, after an upgrade when the
python-bindings changed interface some 1/2 year or so ago.

-- 
Helge Jensen
   mailto:helge.jensen@slog.dk
   sip:helge.jensen@slog.dk
                -=> Sebastian cover-music: http://ungdomshus.nu <=-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org