[Top][All Lists]

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

Re: Sourge Forge Repository Structure

From: Mark E. Hamilton
Subject: Re: Sourge Forge Repository Structure
Date: Fri, 17 Jun 2005 10:06:30 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913

Paras jain wrote:

1. Does this means that the --allow-root of /etc/xinetd.d/cvspserver is containing so many entries for so many repositories.

Note that my experience is with SourceForge Enterprise Edition, not The structures may be different, but probably not by much.

IAE, although there are multiple separate repositories, they all share the same root directory, /sourceforge/cvsroot or /cvsroot (which is a symlink to /sourceforge/cvsroot.) Only these two directories are in the cvspserver file.

2. Whenever they made a new repository they edit /etc/xinetd.d/cvspserver or is 
there any automated way of doing this.

Not needed. See #1 above.

3. Will making hundreds of groups and users in LINUX creates any problem?

UNIX/LINUX is perfectly capable of handlng tens-of-thousands of users and groups (probably even millions, but I'd hate to have to manage a system like that. ;) ) The only issues are those that always come with a large UNIX/LINUX system; managing user accounts, storage, and backups, and these are all people and resources issues, not technical issues.

Jain Pars

-----Original Message-----
From: Mark E. Hamilton [mailto:address@hidden Sent: Monday, June 06, 2005 8:47 PM
To: Paras jain
Cc: address@hidden
Subject: Re: Sourge Forge Repository Structure

Paras jain wrote:

Dear List,
  Source Forge is probably the largest user of CVS, Does any body have idea 
that :
a) whether Source Forge maintain different repositories for different projects 
or single repository containing several projects?

SourceForge uses a different repository (and different UNIX group id) for each project. However, nothing prevents a project admin from hosting multiple products in a single repository/project.

b) What are the Unstable and Stable revisions are they resides in different 
repositories or in a single repository using branching?

The branching methodology is up to each project admin(s). However, if they're using CVS correctly the stable and development revisions should reside in the same repository, with the Stable revision(s) tagged and branched.

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.

reply via email to

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