Garrett Rooney <rooneg@electricjellyfish.net> writes:
> ok, that's it, i've seen yet another post by someone with a problem
> with externals, and i've had it. i've been thinking about this for a
> while, and i'm tired of keeping quiet about it.
>
> can we just get rid of the svn:externals feature?
Unfortunately not. Turns out to be too useful to most folks. But the
Chicago boys have long been envisioning the future of svn:externals.
It goes something like this:
1. Teach Subversion to handle linked working copy from various
repositories (like CVS already does). By "linked", we mean
that in a parent directory there is an actual entry for a given
child subdirectory, but that child subdirectory comes from a
different repository. To date, no part of Subversion's code
allows this to happen. And when fully implemented, it means
that *all* Subversion commands will know how to properly deal
with performing their actions in light of a working copy that
is assembled from various repositories (or repos locations).
2. Make 'checkout' and 'export' the only Subversion subcommands
that do a *thing* with externals. And what do they do? They
checkout/export the external thing, and in the case of
checkout, the external thing is linked to the current working
copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 24 00:59:18 2003