[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: mark benedetto king <mbk_at_boredom.org>
Date: 2003-04-07 07:43:25 CEST

On Sun, Apr 06, 2003 at 01:03:51PM -0500, cmpilato@collab.net wrote:
> Robert Pluim <rpluim@bigfoot.com> writes:
>
> > mark benedetto king writes:
> > >
> > > 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.
> > >
> >
> > Hmm, sounds tempting, but it means that working copies would no longer
> > be completely self-contained.
>
> Correct. -1, unless there is some amazingly brilliant reason to do
> this.
>

The notion of working copies being self-contained with DNS and
network-topology dependent URLs in them is illusory. That's why people
keep asking for "svn switch --relocate".

We've already moved credentials out of the ADM dir. This is the
next logical step. If you don't have any credentials in ~/.subversion, svn
prompts you and moves on. If you don't have any URL for a particular
UUID, svn can prompt you and move on.

IMO, The only purpose that the URL should serve is establishing the RA
connection. Anything else is wrong.

--ben

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 7 07:45:30 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.