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

SV: Re: issue #137

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2006-09-04 10:45:01 CEST

> I think the best (and only?) option is to go with
> global hook scripts specified in the settings
> dialog. Specifying the hook scripts via properties
> just doesn't seem to work in a reliable way.


If we just make sure to post enough parameters to the hook-scripts, the
script will then be able to cater for every individuals special needs.
(For example: By looking at the repos-path of the current action, it
could call a project-specific hook, or it could use SVN-command-line
tools to look for user-defined special properties and do actions
depending on them and so on...)

In a corporate environment with "global" system administration this
scheme provides a maximum of flexibility with very good security.


PS. Simons suggestion seems not to be a bad one, but maybe more suitable
for a "step-two" in the client-hook implementation? I would suggest
going with global hooks first, and iron out all bugs there, before we
start working on more complex ways to call hooks. DS.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Sep 4 10:44:41 2006

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

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