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

Using Externals in a unique dir structure...

From: Bryan D. Andrews <bandrews_at_trendcore.com>
Date: 2006-01-15 19:10:04 CET

We have a project that has a directory structure like so:


There are also other directories that our specific to our development
such as:


This directory represents the core that changes from version to version:


The core also has its own desktopmodules (as well as providers,
httpmodules and controls) included such as:


Currently our main working copy is:


which has all of our custom dev for the \controls, \desktopmodules,
\httpmodules, \providers

We currently export the C:\Projects\DotNetNuke over the working copy so
we can have the full web application in place for testing, debugging,

Because there are shared folders (desktopmodules, etc), for us to use
externals in this situation we would have to use the main
c:\Projects\DotNEtNukeCore folder as the working copy and then create an
externals definition for each subfolder -- which would currently be
about 40 entries. Then when the core version changed, we would have to
redo all these entries... (from what I understand when you switch to a
new tag).

Is there a creative way to do this other than what I have stated? It
would be nice to know that both the core and the custom dev represented
the latest code without having to do the exports I speak of.

Thanks for any tips.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 15 19:11:15 2006

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.