Ben Collins-Sussman <sussman@collab.net> writes:
> 1. as Peter points out, 'svn up' right after setting the property
> does nothing at all... the externals aren't checked out.
Whoa! This was working, and now has stopped working, unless I'm
grossly misremembering. I'll check it out.
> 2. If I check out a module, I end up with a few 'external'
> subdirectories. I'm aware that they aren't directly linked with
> the root working copy. But still, when I run 'svn up' at the top
> of my working copy, the update *never* happens in the external
> subdirs. Your first response might be, "yes, well, the subdirs
> aren't linked, so the update never recurses in there." But this
> seems like a silly cop-out to me; why aren't we just running a
> sequence of updates? It's so easy for 'svn up' to notice the
> svn:externals property when it first starts, and have it queue up
> a separate update for each external. And in my mind, this is how
> a "working copy that's aware it's a module" should behave.
>
> Maybe I should file an "incomplete feature" issue, assuming others
> agree?
+1
> At a minimum, maybe the value of each external can be a string that
> contains a URL and any number of switches... weren't we talking about
> that idea?
Yup, just haven't implemented yet. One of the issues was that
although it's fine to use the command line client syntax, note that
we're _not_ invoking the client as an external process or anything
like that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 03:37:55 2002