On Fri, Feb 28, 2003 at 03:27:15PM -0600, Florin Iucha wrote:
> On Fri, Feb 28, 2003 at 12:48:40PM -0500, mark benedetto king wrote:
> >
> > It it my intention to merge in the issue-951 changes this weekend.
>
> Will this handle svn:externals as well?
>
> florin
>
Not this weekend. :-)
What this thread (and another concurrent thread) are touching on is
the disconnect between the URLs that we are using to refer to these
repositories and their logical names.
Perhaps we should support a new schema: repo:name:/path
The name would be resolved to a URL via ~/.subversion configuration.
Benefits include, but are not limited to:
1.) O(1) svn switch --relocate. Actually, we'll probably want to keep
the crawling version around; people who just want to move the pointer
can simply edit the config file.
2.) implicit support for svn:externals, even in a heterogenous work
environment, where one developer needs http: and another needs svn:
3.) less typing, better usability ("what was the URL for the tomcat repo?")
Drawbacks: WCs are not self-contained; tar up a WC and ship it to your
grandmother, and it might not work for her. We could engineer some of the
pain out of this by prompting for URLs if we enounter unknown repo names...
Note: WCs are not *reallY* self-contained, anyway, since URLs are interpreted
by local resolvers, local DNS servers, local proxies, local routers, etc...
Also, anyone who *wanted* to make a "universal" WC could --relocate it to
a "real URL".
I'm sure there are other drawbacks that don't come immediately to mind;
I have been drinking, after all. (And it's not even 5PM yet!)
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 28 22:49:10 2003