Re: permission problem - cannot checkout

[David Taylor]

Perhaps the scheme outlined at
http://www.cvshome.org/docs/manual/cvs_2.html#SEC30 may be what you're looking
for.:

" ...you could create a single, shared system user for each
        project in your repository, and give each developer their own line in
the `$CVSROOT/CVSROOT/passwd' file. The
               CVS username on each line would be different, but the system
username would be the same. The reason to have different
               CVS usernames is that CVS will log their actions under those
names: when melissa commits a change to a project, the
               checkin is recorded in the project's history under the name
melissa, not pubcvs. And the reason to have them share
               a system username is so that you can arrange permissions in the
relevant area of the repository such that only that
               account has write-permission there."

dtayl

Roni Abusch wrote:

> Thanks Markus, but I have a problem with that - that means that everyone can
> go stright to the reporitory and delete projects\files (even accidentaly).
> Is there a way that everyone will be able to use CVS and it's projects,
> without having permissions to the repository?
> Roni.
>
> -----Original Message-----
> From: Markus Warg [mailto:address@hidden
> Sent: Monday, November 05, 2001 13:30
> To: Roni A.
> Cc: address@hidden
> Subject: Re: permission problem - cannot checkout
>
> Roni,
>
> I'm not a cvs guru, but here is how we got things going:
>
> the repository needs to be group writable for a group that all users,
> that want to access the cvs, belong to.
>
> If all users are in the group "developers", then all files and
> directorys must belong to this group. Directories must be rwx for
> group, too (usually drwxrwxr-x).
>
> Markus

`