This can be done simply by creating a soft link in the main directory, pointer to the subdirectory. Then you can put whatever restrictions on that subdirectory
Lorne On Thursday 06 June 2002 10:29, Noel Yap wrote: > --- Dusan Juhas <[EMAIL PROTECTED]> wrote: > > > I have a CVS folder which I don't want to be > > > > checkoutable (this has been > > > > > achieved simply by chmod the appropriate rights). > > > > However, it has a > > > > > subfolder which I do want people to be able to > > > > checkout/update from BUT > > > > > not > > > being able to commit to. Is this possible to do? > > > > That's quite strange but possible, perhaps. > > You can add a line to the > > $CVSROOT/CVSROOT/commitinfo like this: > > <pattern> $CVSROOT/CVSROOT/<commitscript> > > In response to the original poster, you cannot do this > with permissions since one would have to have access > to the subdirectory in order to check it out. > > Why not create a separate module for the subdirectory? > > Since many things can be missed when using scripts to > perform security functions, I think it's much better > to rely on the OS for such things. > > > > I've tried using LockDir in CVSROOT but to no > > > > avail. I would like to be > > > > > able > > > to set permission per-user and per-file. > > You can use file system ACLs (if you have them) to set > permissions per user (I just posted something on the > FAQ on how to do this). Permissions are on a > per-directory basis, not on a per-file basis. > > Noel > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
