From: Andrew Arnott [mailto:firstname.lastname@example.org]
Sent: Monday, October 18, 2004 11:02 AM
To: François Beausoleil
Cc: Klimek Manuel; email@example.com
Subject: Re: Tree-internal real links
>Thanks for the tip. I didn't know about svn:externals.
>It seems to support pulling in trees from other repositories. While
>that by itself is a good thing, I think the design keeps it from
>solving my problem.
>What I am really looking for is a format of a property like what's
>below (we'll call it svn:internals).
>So the working copy tree would be a subset of the repository tree,
>with all the directories checked-out mirroring the directories in the
>repository. What I'm trying to get away from is having to put the
>"common" and "resources" directory, which are common to many projects,
>as subdirectories inside the "calc" project. Otherwise a check-out of
>the entire repository will get duplicate code into the working copies
>-- as many copies of the common shared libraries as there are
What about this:
/SingleProjCO/calc/projects/calc <where calc is an svn::externals to /trunk/projects/calc
/SingleProjCO/calc/common <where common is an svn::externals to /trunk/common
/SingleProjCO/calc/resources <where resources is an svn::externals to /trunk/common
/SingleProjCO/calc/tools <where tools is an svn::externals to /trunk/common
/SingleProjCO/note/projects/note <where note is an svn::externals to /trunk/projects/calc
/SingleProjCO/note/common <where common is an svn::externals to /trunk/common
/SingleProjCO/note/resources <where resources is an svn::externals to /trunk/common
/SingleProjCO/note/tools <where tools is an svn::externals to /trunk/common
Developer A only wants to build calc
svn co <URI>/SingleProjCO/calc .
Developer B only wants to build note
svn co <URI>/SingleProjCO/note .
Developer C wants the whole enchilada:
svn co <URI>/SingleProjCO/trunk .
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Oct 19 03:31:29 2004