[Top][All Lists]

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

Re: where to put the CVSROOT?

From: Todd Denniston
Subject: Re: where to put the CVSROOT?
Date: Wed, 10 Nov 2004 16:59:08 -0500

ralph wrote:
> Hi,
> I'm not sure if this is a FAQ or not but I couldn't find a good answer on
> it.
> Where should I create my CVSROOT ?
> What is the best location for a cvsroot when you have lots of projects ?
> Which is better :
> projects
>   project1
>     cvsroot
>   project2
>     cvsroot
> CVSROOT = /projects/project1/cvsroot
> or
> cvsroot
>   projects
>     project1
>     project2
> CVSROOT = /cvsroot
> I think the first solution is cleaner because it keeps all files belonging
> to a project together. But is there a good reason not to do it like this ?
> Basically I want to keep all project files together and not having one
> huge cvsroot with everything in it but i'm not sure if i'm using CVS
> correctly then.
> Ralph.
Which is better?
It depends. <you should be laughing now> :)

with method 1 you get maximum flexibility in the way each project has
$CVSROOT/CVSROOT configured. If you have multiple cm or task lead people who
have different ideas on the way a version control system should be ran method
1) will probably help you keep your sanity better. it might also be more
obvious if you happen to use the wrong permissions for a particular project.
This is probably better to use when project1 & project2 are independent of one
This happens to be the way the group I work with does it.

with method 2 there is less explaining to do to users who resent having to use
a version control system at all because when they change projects they only
have to change from doing "cvs checkout project1" to "cvs checkout project2"
without changing their $CVSROOT.  This actually works ok if you have several
very related SUB projects within one project, I know of one of our groups who
has several subprojects and shares code between them this way. It could also
work if you have a very hardened cm/task lead person, i.e., `one repository to
rule them all`.:)

so which is better?
you have to figure out how independent your projects are I believe.
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter
The opinions expressed here are not sanctioned by and do not necessarily 
represent those of my employer.

reply via email to

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