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

Re: externals definition: surprising behaviour

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Thu, 19 Feb 2009 03:33:41 -0600

On Feb 19, 2009, at 03:12, Schroeder, Hartmut wrote:

> I detected a surprising behaviour of externals definition (svn 1.5.5):
>
> - the repository path http://ABC:9090/def/ghi
> has an svn:externals with a value "-r 100 /uvw/xyz xyz"
>
> - checkout of http://ABC:9090/def/ghi
>
> - One can make changes/commits on the working copy of
> http://ABC:9090/def/ghi/xyz,
> and it will take effect on trunk of /uvw/xyz

If there have been no other changes in the place the external points
to, that's true. Otherwise, you would get a message that the
(externals) working copy is out of date, and you would have to "svn
up" the (externals) working copy before being able to commit the
changes.

> , even an update will not
> get
> revision 100 but trunk!

An update in the externals working copy will update the external to
HEAD.

An update in the directory containing the externals definition will
restore the external to its pinned revision.

> But: If I use an explicit revision in my externals I don't want access
> to trunk.
> I think that is a bug cause that may result in instable software.

I believe this behaves as designed. It could probably be improved,
but I'm not sure what specifically should be changed.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1190987

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-19 10:34:47 CET

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