Access Control for seperate source roots?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Subversion allows you with the AuthzSVNAccessFile directive to specify an
ACL; allowing you to define users and groups and permissions on individual
repositories based on that list.

Is there a Chora config option to have my SVN auth. access file be read in and
honored? Or is there a different way to do the same thing within the existing
Chora constructs?

Basically I have two groups; Programming and Operations, and two repositories;
prog and ops, and I want Programming to be able to view the prog repository, 
but not the ops repository, and I want Operations to be able to view both 
repositories.

Any hints?

Augie.


- -- 
Registered Linux user #229905
GPG Public Key: http://www.schwer.us/schwer.asc
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iQEVAwUBQvfqiMcjCXa2d7m4AQgMaggAjySC0o9D6Knu59MqSinmSKrWDvL4PLHd
nvWlIZWa3XwKF7cWbHxSAlN0SkrPgICnNG08941BIfUwpVEHXyE7sLbwgZ1M6gk+
91guqchfFi/zSeybHBQO5vawxwcFWmFwbQb1abPAcYr9Um/JsipEgvkr1qEg+Gnv
AWRJ5WL5xC3NOvrFRtkILNz/VIuJcEJXM0U0F+yWcWlOcnPNU2CEXOmMjj7SzEFN
sucytqn+0X8koXvDBkgUMlw15yzQOqyjV8BA81FPhVjrpRkpUFg9PLcCswzorNK7
zjHa4Y9ZYzKX9DDegSb9qVvIMzKqQ2ov55n/gSg+fquAP/qhrxSPLg==
=f4Ln
-----END PGP SIGNATURE-----
-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]