Hello Cory,
>No. Our current setup is: All developers have separate accounts. They are
>all in a group called "developers". There are staff members who also have
>their own accounts (mine is radcliff), and are members of "staff".
>Therefore, if I give owners and groups R/W access, they can access only
>their own files (they=developers) and my internal staff can access the files
>(because they are in the staff group).
>
>The problem is, when the internal staff members (that are in group "staff")
>commit files that are not owned by them (say, "dev28"), it is leaving the
>group setting as staff but changing the file ownership to "radcliff" or
>whatever staff member committed the file. At this point, the developer can
>no longer read the files because they are neither owner nor in the staff
>group that have permission to read the files.
Well, everybody can be in several groups not just his "main" group. So
I would suggest that you make a new group "cvsusers" and put every
"developer" and "staff" member who should have access to CVS in this
group (/etc/group) without changing their default group. Then they
still have their default groups "developer" or "staff" but are also
members of the happy "cvsuser" family. Now just change to whole
CVS-Tree to group "cvsuser" and everybody should be happy.
>Here's the way the accounts should look:
Much better ... ;-)
Regards,
Norbert
|
