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

Re: Version 1.5

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: 2007-06-01 10:11:40 CEST

On 01/06/07, Lübbe Onken <l.onken@rac.de> wrote:
> Hi si,
> You wrote:
> > What i'd like the post-checkout/post-update hook do is for
> > each directory
> > which contains an App.config.example file in the working
> > copy, check to
> > see if an App.config file exists, and if it doesn't, copy
> > App.config.example to App.config.
> That's what our build script(s) do when they're run for the first time. :)
> When I checkout a fresh WC, I run 'nant <config>' and that's it.
> You also have to install the client side hooks on each and every client. I
> wonder if there would be a smart way to deploy hooks to clients. I'm
> thinking along the line of having a "Client Hooks" repository and a "Client
> Hooks" working copy. Once everything is set up, the users just have to
> update the WC to get the latest hooks, but there would still be no automatic
> deployment.

Auto-deployment of executable code is considered a security risk, in
case someone changes your hook script to "format c:" or some such,
although to be honest it would be just as easy to hide a bomb in a


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jun 1 10:11:47 2007

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