Re: Write Permission

[HMahaffey]

Greetings!

I usually get a lot of very helpful advice when I submit questions out here, 
but this one went unnoticed.  I realize, after reading it, that I wasn't very 
clear, so I thought I'd try again.

I would like to be able to set up my CVS repository so that projects could be 
owned by specific Unix groups.  I'll have scripts that modify the /etc/group 
file so that users can request to be part of various groups (if they are 
approved).  

But say I want to change the ownership of my project to my new, private 
group.  We are using pserver, and this operation is impossible (without a 
"cvs chown" command) without calling the CVS administrator every time.

In fact, when I import a project, it will be owned by my default group.

I suspect this is not a problem for people using SSH.  Do SSH users set up a 
more permissive shell that allows cvs commands as well as "chown", "chmod", 
etc?

Group ownership is a really cool idea.  Is the only real good way to do it 
with pserver to write a commitinfo script that checks the user ID against a 
list of acceptable ID's that can update that module?

Thanks in advance for any advice...

:)hal mahaffey


In a message dated 8/31/00 12:21:33 PM Eastern Daylight Time, 
address@hidden writes:

<< In a message dated 8/30/00 12:35:06 AM Eastern Daylight Time, 
address@hidden 
writes:

> > Is there a way to restrict read/write access for a file based on a group
>  > of userids?
>  
>  not exactly -- access control in CVS is only possible (i.e. by default,
>  and in the obvious easy way) on a per-directory basis.
>  
What are the tricks pserver users employ to set, and later change, those 
permissions?  How do you set the owner on "cvs add" or "cvs import"?  How do 
you change them later without driving your CVS admin crazy?  Should there be 
commands like "cvs chown", "cvs chgrp", .... 

Or should I just switch to SSH?  

 >>