Cheers for that
However, this is not quite what I need. Everyone is accessing in the
same way, but what I need is for the externals definition to match the
location within the project.
E.g. if I have a project trunk at http://myserver/svn/src/project1/trunk
with an external defined as:
When I create a branch/tag from this at e.g.
I would do the same for binaries, but I want the externals to reflect
the same change, ie it becomes:
My other option, other than what I have put in my previous email, is to
create a web-based interface to a branching script which does all this,
but it is messy. My users are using tortoisesvn (actualy they are using
1.1.7 on NT4, coz that's what the apps run on). I thought is I could
intercept requests for the svn:externals property, I could rewrite them
before returning them.
Any more ideas?
From: Blair Zajac [mailto:blair_at_orcaware.com]
Sent: 31 July 2008 18:25
To: Karl Wagner
Subject: Re: Externals with Branches etc
Karl Wagner wrote:
> Hi there
> I have a fairly complicated setup with subversion, keeping both source
> and binaries, with separate trunk/branches/tags directories for each
> project, along the lines of:
See the new relative externals feature:
> 3) A pre-commit script which modifies the externals definition on the
> transaction before allowing it to complete, or a post-commit which
> performs a check out, modifies the externals, and commits. The second
> form of this seems very wasteful, as it would end up creating extra
> revisions, but I cannot find anything which lets you modify a
You can't modify a transaction on the server because the client assumes
what it sends to the server is what will be committed. If you modify
transaction, then it may mess up further communication between the
the server because the two have different ideas on what is in the
This has been checked by www.blackspider.com
Zetex Semiconductors - Solutions for an analog world.
E-MAILS are susceptible to interference. You should not assume that
the contents originated from the sender or the Zetex Group or that they
have been accurately reproduced from their original form.
Zetex accepts no responsibility for information, errors or omissions in
this e-mail nor for its use or misuse nor for any act committed or
omitted in connection with this communication.
If in doubt, please verify the authenticity with the sender.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-01 15:35:04 CEST