Query in using CVS

[Narendhran K]

Hi,
 
I want some details on using Cvs. I have certain modules. I want to give read permissions to certain users on these modules while for other modules they can have write permissions. Is it possible for specifying restrictions on the same repositary for individual users for different modules.
 
The same users  can aslo have write permissions to other modules. 
 
Is it possible to restrict them from seeing other modules .
 
Advice & Help is greatly appreciated.
 
Thanks in Advance
 
Narendhran.K
 
 
Do you Yahoo!?
Free Pop-Up Blocker - Get it now___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: Query in using CVS

[JacobRhoden]

On Fri, 21 Nov 2003 04:23 pm, Narendhran K wrote:
> I want some details on using Cvs. I have certain modules. I want to give
> read permissions to certain users on these modules while for other modules
> they can have write permissions. Is it possible for specifying restrictions
> on the same repositary for individual users for different modules.

Yes it sure is, most people do it by writing scripts to check the persons 
username when they try to checkin a file. Search for commitcheck.pl and you 
will find multiple examples.

Best Regards,
Jacob

___
JacobRhoden -- http://rhoden.id.au/


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: Query in using CVS

[Karl-König Königsson]

This is all very well if you are content with a granularity on module or 
directory level. What if you have branches of your code and want to 
control access to that?

I want, for instance, in my project people to be able to check in rather 
freely in HEAD, but once a version is released (or about to be released) 
we branch the code tree and then there are other rules.

After this point must all checkins go through code moderators and they 
should be the only ones allowed to check into this particular branch.

Is this possible? Or rather: has anyone done this before and is willing 
to share their code/findings?

Cheers!

	Karl-Koenig Koenigsson

JacobRhoden wrote:

On Fri, 21 Nov 2003 04:23 pm, Narendhran K wrote:

I want some details on using Cvs. I have certain modules. I want to give
read permissions to certain users on these modules while for other modules
they can have write permissions. Is it possible for specifying restrictions
on the same repositary for individual users for different modules.


Yes it sure is, most people do it by writing scripts to check the persons 
username when they try to checkin a file. Search for commitcheck.pl and you 
will find multiple examples.

Best Regards,
Jacob
___
JacobRhoden -- http://rhoden.id.au/
___
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

Re: Query in using CVS

[Larry Jones]

Narendhran K writes:
>
> MIME-Version: 1.0
> Content-Type: text/html; charset=us-ascii

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

> I want some details on using Cvs. I have certain modules. I want to give
> read permissions to certain users on these modules while for other
> modules they can have write permissions. Is it possible for specifying
> restrictions on the same repositary for individual users for different
> modules.

Yes, you can do whatever your filesystem permissions allow.  See the
manual for details:



-Larry Jones

Somebody's always running my life.  I never get to do what I want to do.
-- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Query in using CVS

[Stanke, Kay]

Title: RE: Query in using CVS






First of all pardon for non ascii answer but company rules bind me.


The following script is run from our commitinfo hook:


# Please update your path variable with whatever you want to have to get to all

# the tools you need for this script

PATH=/bin:/usr/bin


# This variable contains the list of branches to lock - update this list as per

# your requirement

locked_branches="[INSERT THE BRANCH_TAGS HERE SEPERATED BY BLANKS]"

enabled_user="[INSERT THE CVS_USER_NAMES HERE SEPERATED BY BLANKS]"


# This variable contains the email-ids of people to bug if the checkin fails

# You would probably want to list the ids of the Release Engineers and the CVS admins

people_to_bug="[INSERT VALID EMAIL-ADDRESS TO NOTIFY]"


ErrorExit () {

    Branch=$1


    echo " "

    echo "! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !WARNING ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! "

    echo "! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !COMMIT FAILED ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! "

    echo " "

    echo "${Branch} is closed for commits for ${USER}"

    echo "Please contact $people_to_bug"

    echo " "

    echo "! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !COMMIT FAILED ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! "

    echo " "

    exit 1

}


# This for is probably unnecessary since this script would get two argument - full path to the

# directory where you are doing the checkin and the file you are checking in

for file in $@

do

    # This makes $1 point to the file I am checking in

    shift


    # Grap the 6th field - that contains the branch name. 

   Branch=`grep $1 CVS/Entries | awk -F/ '{print $6}' | cut -c2-`

   echo "Checking permisssions on branch ${Branch} for user ${USER}"

    if [[ ${Branch} != "" ]]

    then

    for locked_branch in $locked_branches

    do

    if [[ ${USER} != $enabled_user ]]

    then

    test ${Branch} != $locked_branch  || ErrorExit ${Branch}

    fi


    done

    else

    fi

    exit 0

done


Perhaps you can use it as a stub and refine it to your needs like generating a notify mail to admins or checking the branch the commit takes place on by a pattern.

Hope this helps. Have fun 

Kay Stanke


Informationstechnologie

Anwendungsentwicklung Web & Data Warehouse


ProACTIV___
CiV Versicherungen t PB Versicherungen t PB Pensionsfonds AG

ProACTIV-Platz 1, 40721 Hilden 

tel  +49 (0) 21 03-34 - 70 26

fax +49 (0) 21 03-34 - 70 29

mailto:[EMAIL PROTECTED] 

internet:   www.proactiv.de 


-Original Message-

From:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED] On Behalf Of Karl-König Königsson

Sent:   Friday, November 21, 2003 9:44 AM

To: JacobRhoden

Cc: cvs

Subject:    Re: Query in using CVS


This is all very well if you are content with a granularity on module or 

directory level. What if you have branches of your code and want to 

control access to that?


I want, for instance, in my project people to be able to check in rather 

freely in HEAD, but once a version is released (or about to be released) 

we branch the code tree and then there are other rules.


After this point must all checkins go through code moderators and they 

should be the only ones allowed to check into this particular branch.


Is this possible? Or rather: has anyone done this before and is willing 

to share their code/findings?


Cheers!


    Karl-Koenig Koenigsson



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs