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

Re: Question on Subversion hooks

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-14 00:16:26 CEST

On Tue, 2004-07-13 at 17:05, Kristis Makris wrote:
> Hello,
>
> I'm trying to add Subversion support to Scmbug, an SCM to Bugtracking
> integration system (http://www.public.asu.edu/~makrists/scmbug/). I'm
> trying to figure out how subversion hooks work. I'm going over the
> documentation on hooks
> (http://svnbook.red-bean.com/svnbook/ch05s02.html) and I am having a
> hard time determining if hooks can be installed externally (i.e. without
> local access to the repository storage location). Is it possible to
> checkout a repository and "check-in" a hook script ?

Nope, there's no analogue of CVSROOT. The hook scripts live in the
repos/hooks/ directory. You need direct access to the repository.

That said, you *could* make that directory into a working copy, and
create a post-commit hook that auto-updates that working copy. :-)

>
> Another question I have is how can I get a list of files that are about
> to be commited using the hook scripts ?

You use a tool like 'svnlook' to examine the pending commit
transaction. 'svn status' and 'svn info' only operate on working
copies, while 'svnlook' operates directly on a repository, and was
written almost expressly for the purpose of being called by hook
scripts.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 14 00:17:51 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.