On Mon, Aug 5, 2013 at 12:49 PM, Ron Wilson <ronw.mrmx_at_gmail.com> wrote:
> On Mon, Aug 5, 2013 at 12:15 PM, Ben Fritz <fritzophrenic_at_gmail.com> wrote:
>> I am thinking about creating a pre-commit hook that EVERY user on my
>> team should use. So it makes sense to me to put it into some
>> repository location independent of what project is being worked on.
>> But if I do this, it will probably never be in anybody's working copy.
>> Can I specify a repository path to a file NOT in the working copy, and
>> have it run as a hook script? Or do I need to stick it on a common
>> network share or something like that?
> Since all your projects are in one repository, you could create a tools
> project and put the various in-house tools your team uses in there. Then
> your uses would have a strong motivation to include that project in their
> checkouts. of course, that means there will likely be multiple copies of the
> tools on each user's PC.
I'm OK with multiple checkouts of the tools...but can't the hook only
access paths that really exist in the repository? Or do you mean,
stick a copy of the tools under each project in the repository itself?
> Another option would be to put commands in the makefile or build script of
> each project that will check for the hook scripts (or tools project) being
> in the working copy and fetching them if they weren't.
That works if the tools project is a subdirectory of everybody's WC
root. But I like checking out just a single "trunk" directory.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-05 19:57:33 CEST