Re: common vs confidential development parts

[Xavier Marichal]

At 23:40 21/12/2001 +0000, Kaz Kylheku wrote:
> In article <address@hidden>, Xavier Marichal wrote:
> >The constraints are
> >A modules should only be accessible to team A
> >B modules should only be accessible to team B
> >C modules should be accessible to all
>
> Try using Unix groups and the appropriate permissions. The A modules are
> owned by group A, and not readable or writable by others. B modules are
> owned by group B and similarly attributed. C modules are world-readable
> and writable. (Or, alternately, are readable and writable only by a generic
> group of CVS users).

I did try that solution (because that would be the simplest solution...) 
but when
a user of group A performs a checkout or a commit, the whole cvs process stops
with an error when encountering any file of group B. Is there a flag to 
activate to
avoid such troubles (ignoring such permissions errors)?

Many thanks for any hint,
Xavier