Re: Issue 1541 - Final [Patch] for svnadmin create --owner --group?

<PING>

Second call for someone to look over my 'svnadmin create --owner --group' patch.
  This may seem like a minor issue, but this patch does the right thing the
first time when creating a repository under *nix-like O/S's. It's a common
complaint from new [to *nix] admins; the book still assumes that the
administrator knows how permissions and ownership operate together.

Log
[[[
Implement two new options to the 'svnadmin create' command to explicitly
create a new repository with rights appropriate for either

1) exclusive access by a single user/process
2) shared access by all members of an existing system group

This is likely to only be relevant to Unix-like operating systems,
where chown(), chmod(), setgid(), and setuid() are meaningful.

* configure.in
     Add tests to check for existance of chown, chmod, setgid, and setuid

* subversion/svnadmin/main.c
     (#include) - need svn_private_config.h in order to get autoconf #define's

     (enum),(options_table),(cmd_table): add owner_id, group_id to option tables

     (subcommand_create): Add logic to get system UID and GID and switch
     current process to those values before calling svn_repos_create()
     Create empty top level repository directory first and change ownership

* doc/book/book/ch05.xml
     (svn-ch-5-sect-2): Add paragraph and link to discussion of --owner and
     --group options in svn-ch-5-sect-5.

     (svn-ch-5-sect-5): Document the use of --owner and --group to create
     the repository with specific rights for limited repository access.
]]]

Thanks

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org