It's better to manage permissions on directories than on files (in fact, it's
probably impossible to manage permissions on files in the general case). So,
group files by permissions. Use directory ACLs to control directory
permissions. Use loginfo scripts to set ACLs of new elements.
An alternative would be to use commitinfo scripts to manage permissions.
Sorry for the vagueness, but I'm in the middle of replanning our ACL/permissions
myself.
Noel
[EMAIL PROTECTED] on 04/14/2000 06:41:19 PM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Fine grained permissions?
I want to know how I can set it up so that I can specifiy access
permissions on a per module and per file basis. For instance, here we
have a web site that contains certain files that have plain HTML and
some that have PHP and HTML. I do not want non-programmers to be able
to modify the PHP pages but I want them to be able to change HTML docs.
I know that I can kludge something like this with multiple repositories
and the use of writers files in the CVSROOT but is there a cleaner way?
- Greg
--
With every passing hour our solar system comes forty-three thousand
miles closer to globular cluster M13 in the constellation Hercules, and
still there are some misfits who continue to insist that there is no
such thing as progress.
-- Ransom K. Ferm
