[Top][All Lists]

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

Re: Help regarding CVS setup

From: Todd Denniston
Subject: Re: Help regarding CVS setup
Date: Mon, 03 Mar 2008 16:49:00 -0500
User-agent: Thunderbird (X11/20071031)

Sadia Tahseen wrote, On 02/29/2008 04:57 PM:
Hello all ,Our lab consists of four dual processor machines running Linux. we have one server with several machines, and all users are set up in the network and are able to access to applications installed in the server , and There are few folders which are made common to all the users ,
One of them is 'appl' for applications.

We want to install the CVS for several users to collaborate in the development of specific computational models .

I assume these computational models are in a computer programming language, such as C, C++, Fortran or lisp.

So I have refered
 various sources for configuring CVS where I
 could learn I have to create another user say 'CVS'.

If I understood you correctly above, all of your users are already setup on all of the systems as real users, i.e, they can login to each one of the machines including (especially) the cvs server machine.

If that is the case you should not need to create another user. Also I suggest against using pserver, so you don't need to do user mapping.

if each of your users can
ssh cvs_server
where cvs_server is the name/ip address of your server machine, then you are half way to getting setup.

So I have a doubt that can't I place a folder in 'appl ' folder which is common to all the users.

is this 'appl ' folder a source folder or a common set of applications they need to build the project?

So I would like to know the how and where to install and other directions to meet my requirements.

Thank you

Further Assumptions:
1) you are root on the server or have sway with the person who is.
2) if you are the root person, you know a bit about Unix administration.
3) if you are using NIS/LDAP A) the cvs_server is also the NIS/LDAP server, B) you know how to map the /etc/* changes I indicate below to NIS/LDAP appropriately. 4) your user name is sadia, the next user in your group is user1..., or you know how to translate those example user names to the appropriate ones on the real system. 5) you and all of your users can secure shell into the cvs_server by typing `ssh cvs_server` pressing enter, and then giving your password or by using ssh-agents. 6) you know how to translate cvs_server and a_workstation to appropriate local machine names.
7) you are needing a quick start to see cvs in action.
8) you'll destroy the repo we setup here, and create one with more appropriate names when you know what you want to do. :)

as root on the cvs_server:
edit /etc/group and add a group for your cvs work, i.e. add a line similar to the following:

then as sadia on cvs_server:
mkdir myExamplerepo
pwd #assumption it returns /home/sadia
export CVSROOT=/home/sadia/myExamplerepo
cvs init
mkdir myExamplerepo/projectdir
chown :sadiascvsgroup myExamplerepo/projectdir
chmod g+rws myExamplerepo/projectdir
#you'll want to tighten up security on the following directory later.
chown :sadiascvsgroup myExamplerepo/CVSROOT
chmod g+rws myExamplerepo/CVSROOT

then as sadia on a_workstation:
export CVSROOT=:ext:cvs_server:/home/sadia/myExamplerepo
export CVS_RSH=ssh
cvs checkout projectdir
date > projectdir/mydate
cvs add projectdir/mydate
cvs commit -m"a comment" projectdir/mydate
ls -R projectdir

You should see something like
CVS mydate

Entries  Repository  Root

as user1 on another_workstation:
export CVSROOT=:ext:cvs_server:/home/sadia/myExamplerepo
export CVS_RSH=ssh
cvs checkout projectdir
ls -R projectdir

You should see something like
CVS mydate

Entries  Repository  Root

now you or user one should be able to add files to projectdir and all of your users can check them out modify and commit version controlled changes to them.

hopefully you and the manual can either take it from here or get us some more specific questions.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Even when this disclaimer is not here, 
the opinions expressed by me are not necessarily sanctioned by and 
do not necessarily represent those of my employer. 
Also even when this disclaimer is not here, I DO NOT have authority to 
direct you in any way to alter your contractual obligation 
and my email can NOT be used as direction to modify a contract.

reply via email to

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