svn:externals best practices

[Bill Arnette <Bi...@signalscape.com>]

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
it.
 
/FooLib/
    include/
    lib/
    doc/
    misc/
 
And a project which depends on FooLib
 
ProjectBaz/
    src/
 
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:
 
ProjectBaz/
    src/
    Dependencies/
       FooLib/
 
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