Re: svn commit: rev 2074 - trunk/subversion/include trunk/subversion/libsvn_wc

On Tue, Jun 04, 2002 at 09:40:45PM -0500, Karl Fogel wrote:
> Greg Stein <gstein@lyra.org> writes:
>...
> > Um. I think having a subdir is a *VERY* useful behavior. Consider my
> > example, with:
> >
> > svn ... urls here
> > svn/neon
> > svn/apr
> > svn/apr-util
> >
> > You can't just say "move svn:external into 'svn'". That namespace is under
> > somebody else's control.
>
> Hmmm. But in that instance, svn would *already* check out its own
> sub-modules. Why would the includer of svn be responsible for that?

I'm throwing out an example, where I've placed components into another
system. Maybe I want specific revisions of the components. Maybe I want them
to use a different URL (e.g. port 81 or a local caching proxy).

Or consider this layout:

   program http://svn.example.com/repos/program
   program/plugins/wongle http://svn.tigris.org/repos/wongle
   program/plugins/bleep http://svn.lyra.org/repos/bleep

In this case, program *definitely* doesn't have references to the
user-defined, optional plugins.

Let's consider this particular case. I am actually doing this on my dev box
right now:

   expat http://svn.libexpat.org/repos/expat
   expat/htdoc http://svn.libexpat.org/repos/htdoc

(the expat docs are not in the dev tree, but (today) are a separate cvs
module)

Need more examples? :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org