----- Original Message -----
From: "Garrett Rooney" <rooneg@electricjellyfish.net>
>
> Actually, I'm thinking of externals within the same repository, so:
>
> your project is http://foo/repos/trunk/myproject
>
> on myproject, you have externals that point to other parts of your tree
> that you use...
>
> libfoo http://foo/repos/trunk/libfoo
> libbar http://foo/repos/trunk/libbar
>
> when you tag trunk, the argument is that the externals should also
> change to reflect that, so after an 'svn cp http://foo/repos/trunk
> http://foo/repos/tags/my-new-tag' you would have the following externals:
>
> libfoo http://foo/repos/tags/my-new-tag/libfoo
> libbar http://foo/repos/tags/my-new-tag/libbar
I never even thought of such a case yet, sorry. I see now that such
a case would cause many problems for the implementation.
Hmmm - for such a case the property probably should be
called svn:internals instead of svn:externals - those projects
are not really external - they're in the same repository.
> > I don't think it should work that way. Just leave the externals on the
> > trunk - that's what the main project used when the tagging occured.
>
> This is the problem, it's unclear how it should work. Some people think
> it's right the way it is, some people do not.
But this problem can be solved by discussing and asking the users.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 23 20:32:04 2003