Quoting Markus Mårtensson <Markus.Martensson@hpc2n.umu.se>:
> Subversion is said to be a replacement for CVS, which is great and much
> needed. We currently use CVS in local repository mode, but with the
> files on AFS (see openafs.org). This works great, ordo the usual problems
> with CVS.
>
> If I am not mistaken, subversion stores the entire repository in a
> Berkely DB which has some support for locking and concurrent access.
> Would it be safe to assume that multiple users could access a
> repository database at the same time on a distributed filesystem?
Only if Berkeley DB works reliably on a distributed FS. Many such filesystems
(notably NFS) don't support locking and mmap well enough. I don't know about
AFS; I'd suggest you look through the BDB docs to see if they have anything to
say about AFS.
> Using AFS for revision control allows us to use the already deployed
> remote file access and security infrastructure instead of introducing
> and maintaining a new one (pserver/webdav).
>
> If it is not currently possible to do, what parts of the code would
> require changes?
If BDB works, you wouldn't need any changes in Subversion. There's one potential
problem regarding file permissions in the repository, though: you'd have to make
sure somehow that files created in the repo by one user cna be read/deleted by
others. The simplest way to do that is to set the group sticky bit on the repos
directories, then put all users in that group and change their umask to 002, but
that may not be what you want. There's been some talk about adding some support
for that into the subversion client itself. If you have any good ideas in this
direction, I'm sure they'd be welcome.
Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 25 13:51:42 2002