On Mar 19, 2008, at 12:43, Farrier, John [USA] wrote:
> I am trying to set up a project that has a core svn archive, and
> many sub-projects (plug-ins). Each of the sub-projects share the
> directory tree with the core. I looked at the svn:externals, but
> that did not seem to address this problem. Consider the following
> as a single svn project directory structure:
> Then, I want to be able to separately manage a third plug-in that
> may not get distributed with the rest of the program, but just to
> some folks. So, I want a second svn project to manage it. That
> being said, I want the final directory structure to look like:
> Now, this single directory structure contains two overlapping svn
> projects. Is there a way to manage these two projects
> independently via svn, but allow them to co-exist in the directory
> tree like this? I would expect the svn repository to present just
> these two projects if all worked as I want...
svn:externals is the way I would do this.
Your repo structure could be like this:
On Program/Source you would set the svn:externals property to
"Plugin3 http://url/to/repo/ProgramPlugins/Plugin3/Source" and on
Program/Inputs you would set svn:externals to "Plugin3Inputs http://
When you check out http://url/to/repo/Program you will get the
directory structure you want.
> When sitting at the "Program" level, I would love for svn to report
> differences in both the core project and the Plugin3 project.
This might not happen, however. You'll have to commit changes to
Plugin3 separately from changes to Program.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-25 13:30:42 CET