Re: file:// + exclusive locking/external locking - what's right?

John P N Pybus said:
> Ben Collins-Sussman wrote:

>> Every year or so Karl says this, and I object. :-) There is a far more
>> important for file:/// to exist.
>>
>> Just as with CVS, an single user should be able to create a personal
>> repository and keep stuff under version control *without* having
>> permission to run a server process. For example, think of a college

> Yes, but in all probability this will be NFS/AFS filestore. You won't
> be able to place svn's Berkely DB's on it anyway...

> sensible policy is to not recommend local use of subversion in such an
> environment.

Ok. Now I'm really confused. Karl says file:// isn't useful except for
testing, Ben says it's your every-day-joe access method, and you're advocating
sticking our heads in the sand cuz it ain't our problem and those people
should just stick w/ CVS?

Just making sure I have my facts straight. I'm still not hearing a consensus.

I know for a fact, that if the 'network' folks ever really caught wind of what
kind of tools/servers run here, we'd have to shut down half the things that
keep our deparment running.

And I *know* I type file:// far more often than I type svn:// or http:// -
except when dealing w/ Subversion itself.

Is it OK to be using file:// or is that protocol eventually going to go the
way of the dodo?

And if so, how come svnadmin doesn't support URLs anyway - no remote admin
allowed?

-- 
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org