AW: Tags and externals

Hi,

if you want an external to point to a specific revision of the target, you can pass a "-r<revision>" in the externals definition. This is what you'd usually do in a tag. The svncopy.pl script (which should be in the contribs section of the subversion svn repository) will help you quite a bit when dealing with a large number of externals.

regards

felix

stephen.3.odonnell@bt.com <mailto:stephen.3.odonnell@bt.com> schrieb am Montag, 8. Januar 2007 10:53:

> Hi I am quite new to subversion and am trying out some things
> to get our project cleaned up a bit.
>
> If I have a repository structure like:
>
> Prod_a
>
> Prod_b
>
> Common
>
> Each of these directories contains a branch, tags and trunk sub-dir.
>
> I use the propset svn:externals command to link common into
> Prod_a and Prod_b and this works as I expected. Then I
> create a branch, and as expected I have to update my external
> link to point to the correct branch of common.
>
> When I want to make a release, I create a tag (with is
> basically another branch), however, when someone changes the
> common branch the tag is updated with the new common code, so
> I have lost my release snapshot. At first I was shocked, and
> then I realised this was clearly going to happen.
>
> So how am I supposed to create a TAG to snapshot my release
> in this situation? I had not intended to put any tags in the
> common code at all, as its never released outside of Prod_a
> or Prod_b. Do I have to change my svn:external link somehow,
> or is there a better way of doing what I want?
>
> Thanks,
>
> Stephen.

-- 
Felix Gilcher
Head of IT Development
Exozet Berlin GmbH
Rotherstraße 20
10245 Berlin
eMail: gilcher@exozet.com
URL: www.exozet.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org