[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn:externals question

From: Eric S <ejs_at_americanlowlife.com>
Date: 2005-04-26 19:44:26 CEST

Is it possible, using externals, to have a subdirectory of a directory
with an externals property to not be external?

We're developing a website, and we're keeping all the code and templates
in subversion. We have the main program in the root directory, and
various subdirectories for logs, support libraries, modules, and
templates. Each of the developers has their own branch, and I wrote a
perl script that walks the developers through a bidirectional merge
between the central devel branch and their personal branch by storing
what versions various branches have been merged from in properties and
then asking for confirmation on the various changes, with more hand
holding for conflicts.

For the most part it all works well, except for one developer, the HTML
author, and that because she doesn't have or want shell access to the
machine that the development work is done on, so her branch isn't kept
up to date with all the code changes that are going on.

To simplify things, I'd like to recreate her branch as a top level
externals property, but then make the templates directory not an
external reference. Is this even possible?

If not, I see two possible alternatives. The first alternative is
moving her templates branch to a different name and creating the new
version of her branch as two externals references, one at the top level
pointing to the devel branch, and one at the templates directory
pointing to the templates directory in her renamed branch. Again, I
suspect that this isn't possible, since I don't want the external on the
templates directory to be in the devel branch, which is where I suspect
it would have to be.

I'm fairly certain the third alternative will work, but it involves a
design change. By moving the main harness code into a subdirectory, I
can then set an externals property on each subdirectory individually.

So, given that I'm rather new to using subversion, any recommendations
as to which approaches are possible/preferable and if there are issues
I'm overlooking?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 26 19:48:16 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.