# Setting up a CVS repository - the FreeBSD way

### Stijn Hoop

`<stijn@win.tue.nl>`

$FreeBSD: release/8.4.0/en_US.ISO8859-1/articles/cvs-freebsd/article.xml 39632 2012-10-01 11:56:00Z gabor $

Copyright © 2001, 2002, 2003 Stijn Hoop

$FreeBSD: release/8.4.0/en_US.ISO8859-1/articles/cvs-freebsd/article.xml 39632 2012-10-01 11:56:00Z gabor $

This article describes the steps I took to set up a CVS repository that uses the same scripts the FreeBSD project uses in their setup. This has several advantages over a stock CVS setup, including more granular access control to the source tree and generation of readable email of every commit.

[ Split HTML / Single HTML ]

# 1 Introduction

Most of the open source software projects use CVS as their source code control system. While CVS is pretty good at this, it has its share of flaws and weaknesses. One of these is that sharing a source tree with other developers can quickly lead to a system administration nightmare, especially if one wishes to protect parts of the tree from general access.

FreeBSD is one of the projects using CVS. It also has a large base of developers located around the world. They developed some scripts to make management of the repository easier. Recently, these scripts were revisited and normalized by Josef Karthauser `<joe@FreeBSD.org>` to make it easier to reuse them in other projects. This article describes one method of using the new scripts.

To make the most use of the information in this article, you need to be familiar with the basic method of operation of CVS.

|  | Next
|  | First setup