info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: permissions on branch


From: Shubhabrata Sengupta
Subject: Re: permissions on branch
Date: Wed, 16 May 2001 08:15:19 +0530

There's a hole in that script though - in its current state it doesn't know
how to lock the trunk. I haven't had time to fix that - maybe you can.

I think you should include the config file in the checkoutlist and control
the config file via CVS, that way you have a history of who changed what in
the config file. The format of the checkoutlist is very simple - one
filename per line you want to keep in checked out state under CVSROOT.

Thanks

Shubho

-----Original Message-----
From: Nils Jakobson <address@hidden>
To: Shubhabrata Sengupta <address@hidden>
Cc: address@hidden <address@hidden>
Date: Tuesday, May 15, 2001 10:17 PM
Subject: Re: permissions on branch


>
>Thanks alot! It works perfect, this is very helpful! And good example on
>cvs scripting, thanks Shubho.
>
>I wonder if I change all the CVROOT config files directly, is there any
>side effects? Just wondering, never used the checkoutlist file.
>
>Nils Jakobson
>SWH Technology
>
>----- Original Message -----
>From: Shubhabrata Sengupta
>To: Nils Jakobson
>Cc: address@hidden
>Sent: Tuesday, May 15, 2001 5:14 PM
>Subject: Re: permissions on branch
>
>
>Well I have to stay back at office a little bit longer, so I though of
sending the script now. I have attached a korn
>shell script with this mail.
>
>Here's what you should do with it.
>a) Check out the CVSROOT directory from your CVS repository
>b) Copy this script over the CVSROOT directory and give it execute
permission for all
>c) Modify the script as per your requirements - should be easy
>d) Modify the checkoutlist file to have an entry for the script and check
in the new checkoutlist file
>e) Add and checkin the script
>f) Make an entry in your commitinfo file for this script and check it in
>Your are done now - hopefully things will work.
>
>Thanks
>
>Shubho
>-----Original Message-----
>From: Nils Jakobson <address@hidden>
>To: Shubhabrata Sengupta <address@hidden>
>Date: Tuesday, May 15, 2001 6:37 PM
>Subject: Re: permissions on branch
>
>How you mean this, the CVS/Entries are on the client side. I'm using RedHat
Linux as repository server
>with WinCVS clients. I have to intercept the commit somehow thru wrapper or
similar and then simply
>refuse the commit if some condition is met. I dont know how exactly CVS
internals work, but please send
>me the scrip.
>
>Thanks!
>-Nils Jakobson
>SWH Technology
>----- Original Message -----
>From: Shubhabrata Sengupta
>To: Nils Jakobson ; address@hidden
>Sent: Tuesday, May 15, 2001 2:38 PM
>Subject: Re: permissions on branch
>
>
>You can do that by writing a script which parses the CVS/Entries file for
the branch info and then restrict the checkin
>if the branch falls in your restricted list.
>
>You would need to plug this script into the commitinfo file, since the name
of the file to be checked in would be passed
>to this script which you would use to parse the CVS/Entries for the branch
info.
>
>You might also like to put this script into some subdirectory of the
CVSROOT directory and put an entry in the
>checkoutlist file so that a copy of the script is always checked out as
soon as you checkin any changes to this script.
>
>I can send you a sample script if you need one.
>
>Thanks
>
>Shubho
>-----Original Message-----
>From: Nils Jakobson <address@hidden>
>To: address@hidden <address@hidden>
>Date: Tuesday, May 15, 2001 4:58 PM
>Subject: permissions on branch
>
>
>
>
>
>Hello, maybe this already has been discussed and there is solution.
>What I'm looking for is how to set permissions on specific branch names,
>i mean, make some branches read-only. This is necessery because
>it happens that wincvs users perform commits where they should not.
>I believe this can be scripted in the CVS, but how and from where to
>invoke it? It could be great to have config file with list of branch_names
>to be treated as read-only.
>Its more the development organization problem, but still.
>
>-Nils Jakobson
>SWH Technology
>
>
>_______________________________________________
>Info-cvs mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/info-cvs
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]