Project Builder has a CVS menu, though all of its options (even the tantalizing Enable CVS Integration) remain grayed out unless you set your project up as a CVS sandbox.
If a project already exists in a repository—perhaps as a worldwide open source project, or as part of an in-house repository at your company—then you need to run cvs checkout from within the Terminal to create a new sandbox directory containing your own personal copy of that project. See checkout.
If you have an existing project not managed by CVS, then you must create a new CVS module for it inside an existing repository, through cvs import (see import), before you can use any CVS commands with it through Project Builder. If you lack access to a repository, you can simply make one on your machine through the commands described in Section 18.2.1.
Most of Project Builder’s CVS menu commands execute basic cvs commands (of the sort described earlier in Section 18.1) on the files or folders currently selected through the Files tab, and then display the results as described in the list below. The Files tab’s CVS Status column (see Section 18.4.3) cues you as to which files you can run the following commands on:
This performs a cvs status on the selected files, updating the symbol displayed under the File tab’s CVS status column as appropriate.
Runs cvs update on the selected files, applying patches ...