File level ACL

Thanks for the suggestions yesterday. However, no solutions were
offered. For a recap:
   dir1/aClass.h (should be readable to all users of the library)
   dir1/aClass.cc (should only be visible to selected users working on
it's library)

Users of the library cannot view the source code in aClass.cc. They can
only read aClass.h. Library developpers can r/w everything.

My understanding is that access controlthrough the Apache interface
can't cut it. mod_auth_svn uses a datafile that can contain directories
only. My suggestion would be to add file patterns as well. For example,
I would say "*.h" is "r" for "*".

It's ironic that CVS does this. (Using proper permissions on the files.)
I can't move to subversion until something equivalent (hopefully
better!) exists.

Cheers, Pierre
Received on Fri Mar 26 14:50:52 2004