--- gabriel rosenkoetter <[EMAIL PROTECTED]> wrote: > On Thu, Apr 18, 2002 at 12:58:18PM -0700, Noel Yap > wrote: > > The answer is a little trickier than this, > actually. > > > > I remember having to put something in loginfo so > that > > ACLs would get properly created from the directory > > (default ACLs aren't appropriate here since you > > probably don't want the directory's execute and > write > > bits to be inherited by the files). > > My memory, though I didn't really push the ACLs > hard, was that I > could set ACLs per module by setting them on the > directories in > $CVSROOT after the module was already created. > > Hrm. Actually, I think I only ever did > all-or-nothing access. > Controlling read/write separately is going to > require a loginfo > dance, come to think of it.
Yeah. I should've been more specific (I just got up from a nap -- so goes the life of the unemployed :-) We wanted to allow some users to have read only access to the repository and I wanted to turn of read access to the other (just 'cos I'm paranoid). Even if it were all or nothing, ACLs would still need to be set for new subdirectories, IIRC. Noel __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
