[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Question about the behavior of svn externals

From: David Moll <davermoll_at_gmail.com>
Date: Tue, 14 Oct 2008 11:33:32 -0700 (PDT)

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?

Thanks,

~Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-14 20:35:50 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.