The New Depot command creates a new depot The portion of the AccuRev repository that stores the entire history of a particular directory tree. See element, version. in the AccuRev repository The directory tree that stores all software configuration management data managed by AccuRev. This data is maintained by the AccuRev Server, responding to requests made through AccuRev client programs. Users never manipulate the repository directly..
You can invoke the New Depot command in any of these ways:
Choose File > New > Depot from the GUI main menu.
Choose Admin > Depots from the GUI main menu to open a Depots tab. Then click the New button.
The New Depot dialog includes basic options (always visible) and advanced options (visibility controlled by a Basic/Advanced button).
Depot Name
No two depots in the same AccuRev repository can have the same name. See User-Specified Names for AccuRev Entities.
Notes (click to view):
This can be done -- but it's risky (it cannot be undone) and it takes some work. You must first remove the existing depot with the desired name from the repository. For details, see "Removing a Depot from the AccuRev Repository" in the AccuRev Administrator's Guide.
Physical location ...
The location you choose here must be on a hard drive on the machine where the AccuRev Server The program that manages the AccuRev repository and handles commands issued by AccuRev client programs. process runs. Be sure that the location does not overlap the location of any other depot, or any AccuRev workspace A location in which one or more users perform their work, using files under version control. Each workspace consists of a workspace stream in the repository and a workspace tree in the user's disk storage. or reference tree A directory tree in users' disk storage that instantiates a particular dynamic stream or snapshot. It contains a copy of the current version of each element in the stream or snapshot. A reference tree based on a dynamic stream can be updated, to incorporate the stream's recent changes.. See User-Specified Names for AccuRev Entities.
If you do not specify a physical location, the new depot is placed under directory storage/depots within the AccuRev installation area.
A depot’s physical location is said to be a slice The subdirectory tree that stores all the data for a particular depot, including the depot's file storage area. By default, the top-level directory of this subtree has the same name as the depot itself. of the overall AccuRev repository . To change the location of an existing depot, use the CLI command chslice.
Files should be case ...
We strongly recommend that you make your depots case-insensitive, for compatibility with Microsoft Windows. Your team might not be using Windows right now, but think about the future.
All depots store names of files and directories exactly as they are originally entered (e.g. WidgetGetCount or cmdListAll). Likewise, AccuRev client programs display these names exactly as they were originally entered. The difference is that:
A case-sensitive depot allows users to create two objects in the same directory, with names that differ only in their case (e.g. makefile and Makefile).
A case-insensitive depot (default) does not allow two objects in the same directory to have names that differ only in their case.
You cannot change an existing depot from case-sensitive to case-insensitive, or vice-versa.
Selecting the exclusive file locking An AccuRev feature that enforces serial development: when a file becomes active in one workspace, an exclusive file lock prevents the file from becoming active in sibling workspaces. option causes all workspaces A location in which one or more users perform their work, using files under version control. Each workspace consists of a workspace stream in the repository, and a workspace tree in the user’s disk storage. created for this depot to use AccuRev exclusive file locking An AccuRev feature that enforces serial development: when a file becomes active in one workspace, an exclusive file lock prevents the file from becoming active in sibling workspaces..
See File Locking.