On Mon, 2003-11-24 at 14:31, John Peacock wrote:
> Because the only time that this is _sufficient_ is when the repository is
> private to the user creating it.
That's not true; and moreover, I'm a bit confused about which use cases
you think your patch will solve.
Use case: I create a private repository for use with ra_local under my
user account. The defaults work fine, as you say.
Use case: I create a repository for use with ra_dav or (non-tunneled)
ra_svn, running the daemon as root. The defaults work fine, no matter
who I create the repository as.
Use case: I create a repository for use with ra_dav or (non-tunneled)
ra_svn, running the daemon as another user. I must create the
repository as the user I'm going to run the daemon as, or chown it after
I create it. Your patch would help eliminate the chown step, but it
seems incongruous; other file creation commands, like mkdir and touch,
do not have owner and group options to remove the need for a chown.
Use case: I create a repository for use with ra_local or tunneled ra_svn
by multiple users. I must create the repository with a group which all
the users are in, ensure that the repository is group-writable, ensure
that the directory is mode g+s on certain systems, and ensure that all
access uses a umask of 002 or 007. How will an option to svnadmin
create help this use case?
(As an aside: I got Keith Bostic to agree that some future version of
BDB should ensure that newly created logfiles share the permissions of
the DB. I hope that solves the majority of our shared-access problem,
though we may have to wait years for it to happen.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 24 21:30:49 2003