Re: issue #137

On 8/31/06, Joseph Galbraith <galb@vandyke.com> wrote:
> I see... I don't see a good solution then.
>
> I think, if it were my call, I'd drop the requirement that
> they be in the wc, force the hook-script to be an absolute
> path, and use the 'get permission first' model to deal with
> security concerns.
>
> Actually, how about this, allow two different kinds of
> paths: absolute local and repository-root relative.
>
> o If the path is an absolute windows path, get permission
> and then run it.

An absolute windows path won't work with project properties - you
don't know the absolute path on every machine the sourcecode is
checked out.
This would only work with a global config file or an entry in the
settings dialog.

> o If the path is repository-root relative, determine
> if the file is contained with in the working copy,
> and warn if not.

to get the repository root, we'd have to contact the repository and
ask for it first. And since I really don't want (and won't do) to
contact the repository in e.g. the commit dialog (start-commit,
pre-commit hooks), this isn't an option either.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org