> Hm, I guess I don't quite understand.... how does your users being
> spread out across the country relate to you wanting them to only get
> the head revision?
>>> What you could do is keep a working copy of the relevant part of
>>> the repository on the server
I guess I took this as there being a separate place they would get (non-svn) access to the working copy, which won't work because there isn't a network file server (so-to-speak).
> Now, you could use Subversion 1.2's new WebDAV mount ability, actually.
> That only shows the HEAD revision.
Yeah, I may need to convert over to using WebDAV rather than svn://, the reasons are mounting. I don't have access to apache on that server, so it's a pain.
Is there a speed difference when using svn:// vs WebDAV over the Internet with large (10MB+) binary files?
Thanks for the feedback.
Ron
Ryan Schmidt wrote:
> On Oct 17, 2005, at 19:42, 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....
>>>
>>
>> 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.
>>
>
> Hm, I guess I don't quite understand.... how does your users being
> spread out across the country relate to you wanting them to only get
> the head revision?
>
> And if they don't have access to the server, how were you wanting them
> to get the files then? Were you wanting them to be able to get a
> working copy or just an export?
>
>
> Now, you could use Subversion 1.2's new WebDAV mount ability, actually.
> That only shows the HEAD revision. You'd need Apache2 for the server
> for that. Your users wouldn't have to get a working copy either, they
> could just mount the WebDAV volume and copy down the tools they need.
> If you wanted to prevent them from modifying the tools, you could do
> that too.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 18 06:39:37 2005