[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: File level ACL

From: Gary Feldman <gary_at_memento-inc.com>
Date: 2004-03-26 19:00:47 CET

----- Original Message -----
>From: Pierre Belzile

>My understanding is that access controlthrough the Apache interface can't
cut it. mod_auth_svn

There's an obvious alternative, which you may not like because it requires
restructuring your tree, but it has certain advantages: Put the .h files in
a separate include directory, and then use Apache's directory protections.

This is a fairly common source tree pattern. It's sometimes done for the
same reason in a different context (i.e., it's easier to manage UNIX
permissions this way). It also makes it easier to set up include flags for
the compiler (e.g. just generate automatically from all the include
directories). It makes packaging of kits easier (just include the /include
directory instead of identifying files individually). It makes it much
easier to verify that permissions are what you want them to be. It makes it
easier to have private include files (instead of using .hh or something
similar). It takes a bit of getting used to, particularly since most people
never learn this approach in school, but it's probably worth it - especially
in your case where you have such a strong requirement.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 26 19:01:19 2004

This is an archived mail posted to the Subversion Users mailing list.