Re: let's kill svn:externals

SteveKing wrote:

> You mean something like this?
>
> Main Project located at
> http://foo/repos/trunk/
> an svn:externals under http://foo/repos/trunk/folder
> pointing to
> http://goo/repos/trunk/
>
> now do an svn copy from the working copy of the main project
> to http://foo/repos/tags/newtag
>
> And now you want that the svn:externals points to
> http://goo/repos/tags/newtag
>
> ?

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 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.

-garrett

---------------------------------------------------------------------
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:20:16 2003