> -----Original Message-----
> From: Steve Williams [mailto:stevewilliams@kromestudios.com]
> Sent: Thursday, August 11, 2005 11:24 AM
> To: Rob Anderson
> Cc: users@subversion.tigris.org
> Subject: Re: Read only checkout settings
>
> > Is there a way to make read-only checkouts possible on a
> > per-repository basis? At the moment it seems to be only settable on
the
> > client side and it applies to all repositories. What would be nice
would
> > be to set this up on a server-side configuration.
>
> I assume you mean that you do not want them to have commit access.
That
> is easily configured server-side. The Subversion book shows how to do
it.
>
We have two sets of data under revision control.
source data, from which we build target data (for want of better
phrases)
Users can
1. Checkout target data to a local dir, or
2. Checkout both source and target data, modify source data and build it
into the local target data dir, and test locally.
We want the source data to checkout read-only because we enforce
exclusive locking on it (it's binary data like textures, 3dsMax files
etc...), but because of 2. above we want the target data to be
writeable. Whether or not the repository for the target data is
writeable is not important at the moment. Eventually we will have a
remote build server which will build target data from source as it's
checked in, or when local users request remote builds, so we will
probably at that point want.
Thanks
Rob
________________________________________________________________________
This email has been scanned for all viruses on behalf of Juice Games
Ltd by the MessageLabs Email Security System. _______________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 11 12:55:46 2005