Re: svn:externals

> I ... am so confused. Can you give a full example of where these
> problem is hurting you, using real (or at least real-looking) URLs and
> working copy paths and such? Sorry if I'm just dense today.

Ok, I'll try to explain.

We have in our company several projects under version control.
And (currently only) one of those projects is a library which is
used in several other projects. Those projects have that library
checked out with the svn:externals property.

http://svn.intranet.com/svn/project1/
http://svn.intranet.com/svn/project2/
and the library
http://svn.intranet.com/svn/library/

the working copy looks like this:

project1
  /src (svn:externals library http://svn.intranet.com/svn/library)
    /library
    /main
    ...

project2
  /src (svn:externals library http://svn.intranet.com/svn/library)
  /library
  /main
  ..

now it happens often that during the work on the project
that the library gets updated too (bug fixes, new functions)
and that gets committed too.

since both projects are under development the library is
always updated to HEAD.

Now one of those projects reaches a point where a tag
is required. This is done with

svn copy project1 http://svn.intranet.com/svn/project1/tags/sometag

and since the svn:external tag does not have the revision of
the library a later checkout of
http://svn.intranet.com/svn/project1/tags/sometag
will check out the library from HEAD instead of the revision it
had when doin the copy.

hope it's more clear now what I mean...

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 24 18:37:18 2003