Dovetailing issues 960, 951, 926, etc (URLs in WCs)

I have a WC with the changes for issue-951 (switch --relocate) merged in,
ready to commit.

I realize now, though, that the changes are wrong.

We shouldn't be rewriting the URLs in the WC.

We shouldn't do this because we shouldn't have URLs in the WC at all!

Issue 960 calls for the separation of repository URLs from the path
components in the WC.

(from issue 960):

        Instead of ...

                url="http://svn.collab.net/repos/svn/trunk/www/blah"

        ... something like ...

                repos="http://svn.collab.net/repos/svn"
                path="/trunk/www/blah"

This is good; it removes the information-loss. But it could be better;
unfortunately, the URLs that users use to reference a particular repository
can change over time, sometimes frequently, which is what issue-951
addresses.

What if, instead, we had a ~/.subversion/repositories file, which
looked something like this:

[d8f54182-2d6f-4092-bc72-42359026ff08]
name = svn-dev
description = The Subversion Development Repository
url = http://svn.collab.net/repos/svn

Then the repository URL could be looked up via the WC UUID.
The user could easily change the URL with their Favorite Editor when
they need to. Or a cmdline util to manage the known repositories
could be created.

Nameless, descriptionless entries could be created automatically on
the first connection to a particular repository.

Further, URL targets would no longer need to be specified "long-hand";
one could simply "svn co :svn-dev:/trunk".

The "CVSROOT" feature mentioned in issue-926 could also be provided, via
syntax like "svn ls ::/branches".

--ben

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 6 00:11:57 2003