> There isn't a pre-checkout script, that's true.
>
> What you could do is keep a working copy of the relevant part of the
> repository on the server, and automatically update it every time
> someone commits, via a post-commit hook. Then, for the people who
> should only be able to get things from head, have them use this working
> copy. Of course, they could then only look, not do any Subversion
> operations, like modify and check back in....
My users are spread out all over the country and work from home, so they don't have access to a server to pull down a working copy. That is what I was trying to use subversion for, to help with this process.
Sounds like I'll need to look for a better/different solution.
Thanks.
Ron
Ryan Schmidt wrote:
> On Oct 17, 2005, at 18:39, Ron wrote:
>
>> Is there a way to prevent (via a hook or some other mechanism) a user
>> from pulling down older revisions of a file. I am using svn to
>> distribute binary tools to a large number of users, but I don't want
>> (some of) them to be able to pull down older versions, only the HEAD.
>>
>> I'm using the svn:// protocol.
>>
>> Is this possible?
>>
>> I don't see a hook script for trying to pull down a revision, but
>> this would be a nice one to have, although it might slow things down).
>
>
> There isn't a pre-checkout script, that's true.
>
> What you could do is keep a working copy of the relevant part of the
> repository on the server, and automatically update it every time
> someone commits, via a post-commit hook. Then, for the people who
> should only be able to get things from head, have them use this working
> copy. Of course, they could then only look, not do any Subversion
> operations, like modify and check back in....
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 17 19:46:16 2005