Thanks for the information. I didn't see anything in ViewCVS that would
support access control, but I just wasn't sure.
As far as a browser-based checkin/checkout, I guess that doesn't really
make much sense to begin with. Since there is essentially no working
directory, the browsing tool would need to play tricks like creating a
temporary workspace into which the upload would be accepted and then
committed. If this was a good idea, then I'm sure ViewCVS would have
implemented it long ago for CVS repositories.
Thanks,
Tony
On May 21, 2004, at 3:22 PM, C. Michael Pilato wrote:
> Anthony Glover <gloverae@elmco.com> writes:
>
>> I just got ViewCVS installed and was browsing my repository when I
>> noticed that my access controls that I had set up for Apache are being
>> ignored. I guess this makes sense since I am not using the Location
>> specified in my httpd.conf, but am instead using the viewcvs.cgi
>> script instead. Is there anyway to implement access controls such that
>> even "file:" access (which I'm assuming that viewcvs uses) is
>> controlled?
>
> ViewCVS uses direct access via the libsvn_repos and libsvn_fs
> bindings, and has no built-in access control interface.
>>
>> Also, I'm not that familiar with ViewCVS...does it support checkout
>> and checkin of repositories?
>
> No. It's just a repository viewer.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 22 00:01:09 2004