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

svn:externals best practices

From: Bill Arnette <BillA_at_signalscape.com>
Date: 2005-10-06 16:10:08 CEST

How should svn:externals be set up if you want to include subdirectories of
another directory.
What is the better practice?
Have the externals create the intermediate directories or create the
intermediate directories on the project which needs the dependencies?
Ex. Given a 3rd party library called FooLib, we create a vendor branch for
And a project which depends on FooLib
Now we want to set an external to FooLib in a Dependencies directory, but we
only want the include and lib subdirectories. Is it better to set the
externals on ProjectBaz like this:
Dependencies/FooLib/include svn://myrepos/FooLib/include
Dependencies/FooLib/lib svn://myrepos/FooLib/lib
Or should the ProjectBaz directory have a Dependencies/FooLib directory:
where the externals are set on FooLib like so:
include svn://myrepos/FooLib/include
lib svn://myrepos/FooLib/lib

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 6 16:19:07 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.