Re: Web projects, commit problems & repository access

Philip Reynolds <phil@Redbrick.DCU.IE> writes:

> Checking out the source in our home directories, would mean that
> changes go to the source first, which are then committed but then
> have to be checked out on the main source page then. This is rather
> cumbersome, especially in the development of a new system, where
> changes are constantly being made.
>
> What alternatives have people had with this?

This is classic. Create a post-commit hook script that runs 'svn up'
in the "live web" working copy.

> svn, version 0.16.0 (r3987)
> compiled Feb 7 2003, 14:28:10
>
> on FreeBSD 4.7-STABLE

This is five releases behind, quite scary. You really should be using
0.17.1!

> Ok, one last problem I can't seem to fix, is the issue where
> ``user1'' creates a repository (svnadmin create) and wants to allow
> ``user2'' full access to it (adding, reverting, deleting,
> commiting).

Yes, use Unix permissions. This is a basic Unix permissions problem.
Create an 'svn' group and make the repository owned by that group.
Make sure all the developers are in the group, and use sane umasks. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 13 22:11:13 2003