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

Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please

From: Mike Dixon <michael.dixon_at_denovosoftware.com>
Date: Tue, 27 Oct 2009 10:31:35 -0700

David Corley wrote:
> 2. Assuming 1) is true, are there valid reasons why SVN would allow a
> repo to have an svn:external reference to itself?

Certainly. The svn:externals syntax even includes a shorthand for "this
repository"; use ^ in place of /path/to/repo.

For example, laying out your repo like this:

   /
   /libs
   /libs/lib1
   /libs/lib2
   /projects
   /projects/project1/
   /projects/project1/libs

Then you set svn:externals on /projects/project1/libs to

   ^/libs/lib1 lib1
   ^/libs/lib2 lib2

This allows you to have multiple projects that use shared libraries,
while avoiding having the library code duplicated inside each project.

Of course, you have to be careful when setting it up, as it can lead to
the recursive situation you ran in to.

-Mike

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2411737

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-27 18:32:44 CET

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