On Mon, Aug 5, 2013 at 1:56 PM, Ben Fritz <fritzophrenic_at_gmail.com> wrote:
> On Mon, Aug 5, 2013 at 12:49 PM, Ron Wilson <ronw.mrmx_at_gmail.com> wrote:
> > 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
> > 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?
I mean that besides the "real" projects in your repository, there would be
a distinct tools project. Your users could either explicitly check out that
project along with whatever projects they are working on, or you could
automate the checkout of the tools project in your makefiles or
> > Another option would be to put commands in the makefile or build script
> > each project that will check for the hook scripts (or tools project)
> > 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.
Maybe an extern reference in each project to the tools project would
satisfy TSVN's restrictions. Otherwise, the alternative is to maintain
multiple copies of the hook scripts in each project. Seems to me an extra
project containing the common elements is a small price to pay.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-05 20:18:26 CEST