Your structure really suggests you need to move your branch points up. The
project1 trunk should include src and bin. As a side effect, then you can use
relative externals. But the key point is that you're branching both at the same
time anyway, so that moving trunk to include src and bin will reflect that.
Branching and tagging in svn is an extremely cheap operation and even if you
check multi-gigabyte files into bin and branch or tag it, it will consume no
additional space. So if you designed your repository for that reason, you don't
have to.
Regards,
Blair
Karl Wagner wrote:
> 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:
> dir1 http://myserver/svn/bin/project1/trunk/dir1
>
> When I create a branch/tag from this at e.g.
> http://myserver/svn/src/project1/branches/mybranch
> I would do the same for binaries, but I want the externals to reflect
> the same change, ie it becomes:
> dir1 http://myserver/svn/bin/project1/branches/mybranch/dir1
>
> 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?
>
> Regards
> Mouse
>
> -----Original Message-----
> From: Blair Zajac [mailto:blair_at_orcaware.com]
> Sent: 31 July 2008 18:25
> To: Karl Wagner
> Cc: users_at_subversion.tigris.org
> 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:
>
> http://subversion.tigris.org/svn_1.5_releasenotes.html#externals
>
>> 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
>> transaction.
>
> You can't modify a transaction on the server because the client assumes
> that
> what it sends to the server is what will be committed. If you modify
> the
> transaction, then it may mess up further communication between the
> client and
> the server because the two have different ideas on what is in the
> revision.
>
> Regards,
> Blair
---------------------------------------------------------------------
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 20:10:04 CEST