Re: CVS Modules/ SVN Externals

Hi Corris,

I'm too have found my only gripe with svn so far is the limited abilities of
svn:externals.

> Ideally we'd like to tag a "module" which
> would tag the source, and all the shared components.

in a previous mailing list post, someone pointed out that there's an optional in
the svn:externals definition to add a revision number to the URL eg:
foo/bar -r 1234 http://example.com/repos/zag
(this is documented in "svn help propset", but not in the Book, strangely)

So one approach would be:
1. Create your tag by svn copying the project to a tag URL.
2. Check out the tag URL, and modify each svn:externals definition to point to
the correct revision (or tag) of the shared code they import.

A bit cumbersome, but at least it means you have full control over which
tag/revision you use of each imported bit of code.

I don't think the svn:externals is something the developers have put much effort
into yet - I pointed out that they don't really work if you're using port
forwarding through ssh the other day, and got no response.

cheers, Patrick.

-- 
Patrick Sunter
--------------
Visitor in Geophysics
Center for Advanced Computing Research
Mail Code : 158-79
California Institute Of Technology,
Pasadena, CA 91125, USA.
Ph : +1 (1) 626 395 2565
Fax : +1 (1) 626 584 5917
E-Mail : patrick@cacr.caltech.edu
--------------
Project Coordinator & Software Engineer
Victorian Partnership for Advanced Computing
E-Mail: patrick@vpac.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org