How can I branch in SVN and have it branch my svn:external folders as well?

Asked 29/10, 2008 at 0:10 Answered 29/11, 2011 at 8:39

I'm using tortoise svn in Windows.

Androus answered 29/10, 2008 at 0:10 Comment(2)

Here is a blog post which talks about this very problem and the potential work-arounds... thinkinging.com/2008/10/21/… – Orozco 23/5, 2012 at 18:54

Here is an windows command line utility which freezes externals for branching/tagging: svnxf.codeplex.com – Orozco 23/5, 2012 at 19:2

You should use svn:externals as external references from different repositories. So svn:externals should refer to components, modules, 3rd party tools, etc.

You should not use svn:externals to emulate a "symbolic link"-behaviour by using externals to point into the same repository. You can solve such issues most of the time by modifying your build-structure, or use checkout-scripts and sparse checkout feature.

svn:externals have a lot of problems most of them are difficult to see, track and repair: see an example here

commits cannot span over externals(no atomic commits)
branches will not branch their externals(as you pointed out)
tags will not "freeze" their externals so latter builds may result in different/broken builds
merging and reeintegrate merge will not work on externals

If you use externals to point to other repositories, you will most of the time do not have these problems.

Bueschel answered 29/10, 2008 at 20:49 Comment(2)

The issue is that there are scenarios when you actually need externals to the same repo, especially when the system needs components dynamically and a build tool would be an overkill. I've ran more than a couple times in these kind of scenarios for bigger sized projects. – Cirrhosis 11/6, 2012 at 11:16

One solution probably worth looking into is a GIT-SVN setup. And then maybe using git for the cloning part and still keep SVN Externals. – Cirrhosis 11/6, 2012 at 15:28

You'll have to manually create a branch in your external repository and then change your svn:external property to point to the correct branch.

Vietnamese answered 29/10, 2008 at 0:28 Comment(2)

this is not feasible for me because I have a lot of svn:externals in my project – Androus 29/10, 2008 at 0:30

Feasible or not, this is the only solution. It has been requested that is be made an automatic feature of SVN itself but the issue is still open, and quite old... subversion.tigris.org/issues/show_bug.cgi?id=1258 – Orozco 23/5, 2012 at 18:52

When you create a branch within Subversion you are simply creating a cheap copy of the trunk, branch, or tag that you are branching from. This cheap copy will contain all of the same files and properties as the trunk, branch, or tag that you branched from until you begin to modify the properties or files of the new branch.

However, you may be able to modify one of the 'commit' hooks to modify settings automatically once you commit your branch. http://svnbook.red-bean.com/en/1.1/ch05s02.html

Otherwise if you want your externals to be modified on the branch you will need to do so manually.

Dew answered 29/10, 2008 at 0:20 Comment(1)

Modifying an svn-commit transaction via hook scripts is not advisable and not supported by the svn community. It will result in serious workingcopy desynchronisations! – Bueschel 29/10, 2008 at 20:40

there are relative externals now. though you should know :) im using them right now - in the middle of solving a few troubles i got, but im progressing. i just tagged a project after creating relative externals inside it. for now its wierd - when i check out the branch, it notifies me the externals are from revision "top revision of the trunk", but the externals themselves are the original ones - which is what I want :)

Wrestling answered 29/11, 2011 at 8:39 Comment(1)

FYI, I am having trouble with my relative externals. subversion.tigris.org/issues/show_bug.cgi?id=4150 #440166 – Infest 21/8, 2012 at 21:10

Recommended topics

Hot tags