Multi user

2003-03-11 Thread Murali Potla
Hi All, How to set up a repository so that only some users will have permissions to write and some other read access. What should be the permissions of the directory. Where i can i find a good document regarding cvs permissions Thanks Murali ---SOFTPRO DISCLAIMER-

Re: Multi user

2003-03-11 Thread Mahantesh M Vantmuri
Murali Potla wrote: How to set up a repository so that only some users will have permissions to write and some other read access. What should be the permissions of the directory. Where i can i find a good document regarding cvs permissions You can make use of standard unix permissions on modules.

Re: Multi user

2003-03-11 Thread Larry Jones
Murali Potla writes: > > How to set up a repository so that only some users will have permissions > to write and some other read access. What should be the permissions of > the directory. It's somewhat terse, but everything you need to know is in the manual:

Multi-user working directories

2001-01-08 Thread Wayne_Johnson
We're using CVS client/server with :pserver:. We are about to turn our product source over to support. Up until now, a single person has been maintaining the "official release" working file set. After the transfer, we would like to have multiple people doing updates and various other CVS fun

CVS in multi user environment

2004-01-23 Thread Keyser Soze
(I attempted to post the yesterday but I did not see it on the list. Sorry if I repeat myself) I have been tasked to set up CVS on a linux box and will have about 10 users accessing the sourcecode database from various clients (windows, linux, solaris...) Is there a GUI utility for the admin s

Re: Multi-user working directories

2001-01-08 Thread David H. Thornley
[EMAIL PROTECTED] wrote: > > We're using CVS client/server with :pserver:. > > We are about to turn our product source over to support. Up until now, a single > person has been maintaining the "official release" working file set. After the > transfer, we would like to have multiple people do

Re: Multi-user working directories

2001-01-09 Thread Wayne_Johnson
ot. Alex Holst <[EMAIL PROTECTED]> on 01/08/2001 08:56:48 PM To: Wayne Johnson/MINN/Candle@Candle cc: Subject: Re: Multi-user working directories Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > We do have procedures for having people develop the fixes on private working > files.

Re: Multi-user working directories

2001-01-09 Thread Derek R. Price
[EMAIL PROTECTED] wrote: > Thank you. Yes I do know about branches and merging branches. How does this > solve my problem? > > I need to create a set of binaries from our GA branch. The GA branch has been > checked out and built previously (the "Official Release" files). The question > is how

Re: Multi-user working directories

2001-01-09 Thread Wayne_Johnson
01/09/2001 09:44:56 AM To: Wayne Johnson/MINN/Candle@Candle cc: Alex Holst <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Multi-user working directories [EMAIL PROTECTED] wrote: > Thank you. Yes I do know about branches and merging branches. How does this > solve my prob

Re: Multi-user working directories

2001-01-09 Thread Alex Holst
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > Thank you. Yes I do know about branches and merging branches. How does this > solve my problem? > > I need to create a set of binaries from our GA branch. The GA branch has been > checked out and built previously (the "Official Release" files).

Re: Multi-user working directories

2001-01-09 Thread Derek R. Price
[EMAIL PROTECTED] wrote: > The problem here is that we can't check it out every time we want to re-release > the code. There are thousands of modules that would need to be re-compiled. We > need to update the code that was already checked out and run make to build the > updated modules. We the

Re: Multi-user working directories

2001-01-09 Thread David H. Thornley
[EMAIL PROTECTED] wrote: > > Maybe I didn't explain things completely. With the Open Software model, the net > result of a development is a set of source code. In a closed system, we must > ship executables created from the source. (I'm not making any statement here as > to either model being

Re: Multi-user working directories

2001-01-09 Thread Wayne_Johnson
Derek R. Price" <[EMAIL PROTECTED]> on 01/09/2001 10:19:28 AM To: Wayne Johnson/MINN/Candle@Candle cc: Alex Holst <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Multi-user working directories [EMAIL PROTECTED] wrote: > The problem here is that we can't c

Re: Multi-user working directories

2001-01-09 Thread Larry Jones
[EMAIL PROTECTED] writes: > > Thank you all for your time and patience. Looks like there might be an opening > here for a future feature. Something like an override userid option or > environment variable. Something that says, use this userid, not the one on > CVS/Root. If all the files come

Re: Multi-user working directories

2001-01-09 Thread Wayne_Johnson
Great. That works! That solved the problem. I didn't realize that -d overrode CVS/Root. Thanks. [EMAIL PROTECTED] (Larry Jones) on 01/09/2001 11:46:52 AM To: Wayne Johnson/MINN/Candle@Candle cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Multi

Re: CVS in multi user environment

2004-01-23 Thread Michal Goralczyk
Is there a GUI utility for the admin side of CVS for setting up users and projects and such? Most GUI interfaces I known, allows only to specify cvsroot path. For more advenced config you must use emacs ;-) Also, does each user need a regular account on this linux box, or can I set up each user to

Re: CVS in multi user environment

2004-01-23 Thread Larry Jones
Michal Goralczyk writes: > > You don't need system account for each user. You can manage users by > passwd file. In that case you need one system account to map all cvs users. But that's a very bad idea since you lose all OS permission settings and accountability. -Larry Jones Summer vacation