David Moll wrote:
> Hi,
>
> I just recently set up some externals in our source tree for other
> projects in the same repository, so that we could have some libraries
> pinned to a specific revision. For example, our repository has the
> structure:
>
> /trunk/Apps/TS/Gecko/
> /trunk/Libraries/
> /trunk/Libraries3rdParty/
>
> And the head revision is 4209.
>
> The Libraries project is used by Gecko, but it is also under active
> development. Occasionally this causes Gecko to break, and I'm trying
> to avoid that. So I added an external property to /trunk/Apps/TS/ as
> follows:
>
> Libraries3rdParty -r4059 ^/trunk/Libraries3rdParty
>
> When I perform an SVN update on /trunk/Apps/TS/ it creates and
> populates /trunk/Apps/TS/Libraries3rdParty/ with revision 4059.
> That's what I expected. If I then perform an update on the new
> folder /trunk/Apps/TS/Libraries3rdParty/ it is updated to revision
> 4209. Performing an update on /trunk/Apps/TS/ reverts /trunk/Apps/TS/
> Libraries3rdParty/ to the 4059 revision.
>
> Does the /trunk/Apps/TS/Libraries3rdParty/ folder need its own
> property to keep it pinned to rev4059 regardless of what folder I
> choose to use as the target of an SVN Update command?
An external folder is its own working copy. If you update the external,
it doesn't have the pinned revision (that revision is set in the
property of the parent working copy).
And working copy folders don't have a pinned revision at all -
Subversion does not support something like that.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-10-15 18:34:54 CEST