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

RE: Copy externals when branching

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 12 Mar 2009 12:48:16 -0400

I'm not sure I understand what you are wanting to do. So, in trunk you
have externals that point to a foreign repository of some 3rd party
library/tool. But, when you branch you want to be able to modify the
code of the external tools without it being committed back to the
foreign repositories?

 

But, you also want the branches to be dynamically updated when the
foreign repository is modified? But, you want to be able to merge back
to those foreign repositories?

 

I mean, this sounds like exactly the problem a vendor branch is set up
to solve. To allow you to have a copy of the vendors code in your
repository and be able to edit that vendor code and then later merge in
vendor's updates.

 

I also did a quick google and found this http://piston.rubyforge.org/
not sure if it will help.

 

BOb

 

 

 

Let suppose I would like to have a repository structure like this:

- repository root
...trunk
......dir1
......dir2
......dirExt1 svn:externals -> https:/path/to/an/external/repository
......dir3
......dirExt2 svn:externals ->
https:/path/to/another/external/repository
...tags
......v20090101
.........dir1
.........dir2
.........dirExt1 svn:externals -r12345 ->
https:/path/to/an/external/repository
.........etc.
...branches
......ourDev_20090101
.........dir1
.........dir2
.........dirExt1 (??)
.........dir3
.........dirExt2 (??)

My needs can be summarized as follows:
3) now the challenge: if I define a branch (i.e. ourDev_20090101), I
would like
that some/all svn:externals definitions are replaced by actual
directories on *our* repository. On other
words, once I have branched our repository, the development of dirExt1
dirExt2 has to continue on *our* rep.
No references to external repositories should then appear. However, it
would be nice if later a merge back to them would be possible ;-)

Vendor branches may represent a solution, but they make more sense if
you
stick your whole development to a stable version of the external
libraries (like in the example
given in the SVN-documentation).

I am wondering it there exists a smarter solution... Do you know one?

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-12 17:49:14 CET

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.