[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: si <sshnug.si_at_gmail.com>
Date: 2007-06-06 05:24:06 CEST

Hey Lübbe,

Thanks for the reply and sorry for the lag (crunch time at work).

> > 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.

We only use nant on the build server (ccnet) which calls msbuild
for the actual compilation, but yes, I guess I could create a pre-build
task in ms-build to do a similar job.

It would be nice to give the user a heads-up though (e.g. a dialog box)
to say that they now need to configure the following X configuration files
before running.

> 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.

Yup, that's the approach I'd take too. We already version our tools
(NUnit, Log4Net etc), so i'd put the client-side hooks into our tools
working copy.

Also, Simon, thanks for the info on release date.

peace
si

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Jun 6 05:24:16 2007

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