Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > Copy externals when branching

subversion
Discussion topic

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Back to topic list

Copy externals when branching

Author max <iprmaster at gmail dot com>
Full name max <iprmaster at gmail dot com>
Date 2009-03-12 07:25:15 PDT
Message [I have already tried to post this message two times, but it always appeared
as attachment. I hope that this time it will properly work.]

Hi everybody,

I have a problem on how to handle svn:externals in case of repository
branching.

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

- repository root
...trunk
......dir1
......dir2
......dirExt1 svn:externals -> https:/path/to/an/ex​ternal/repository
......dir3
......dirExt2 svn:externals -> https:/path/to/anoth​er/external/reposito​ry
...tags
......v20090101
.........dir1
.........dir2
.........dirExt1 svn:externals -r12345 ->
https:/path/to/an/ex​ternal/repository
.........etc.
...branches
......ourDev_20090101
.........dir1
.........dir2
.........dirExt1 (??)
.........dir3
.........dirExt2 (??)

My needs can be summarized as follows:

1) in trunk the svn:externals definitions should *always* point the HEAD
versions of the external
repositories -> AFAIK this is automatically done if I define "unversioned"
svn:externals

2) in any tag versioned svn:externals definitions have to be set: I have
just
discovered svncopy.pl, so this is not an issue either :D

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?

Thanks,
Max
Attachments
attachment-1628787

« Previous message in topic | 1 of 3 | Next message in topic »

Messages

Show all messages in topic

Subject
Author
Full name
Date posted
+
Copy externals when branching max <iprmaster at gmail dot com> max <iprmaster at gmail dot com> 2009-03-12 07:25:15 PDT
     RE: Copy externals when branching pilotbob Bob Archer 2009-03-12 09:48:21 PDT
     Re: Copy externals when branching David Weintraub <qazwart at gmail dot com> David Weintraub <qazwart at gmail dot com> 2009-03-12 10:19:00 PDT
Messages per page: