The standard configuration rules

The two configuration rules in the default config spec appear in many examples. The CHECKEDOUT rule lets you modify existing elements. If you try to check out elements in a view that omits this rule, you can do so, but cleartool generates the following warning:

nc cmd.c
cleartool: Warning: Unable to rename "cmd.c" to "cmd.c.keep": 
Read-only filesystem.
cleartool: Error: Checked out version, but could not copy to "cmd.c":
File exists.
Correct the condition, then uncheckout and re-checkout the element.
cleartool: Warning: Copied checked out version to "cmd.c.checkedout".
cleartool: Warning: Checked-out version is not selected by view.
Checked out "cmd.c" from version "/main/7".

In this example, the config spec continues to select version 7 of element cmd.c, which is read-only. A read-write copy of this version, cmd.c.checkedout, is created in view-private storage. (This is not a recommended way of working.)

The /main/LATEST rule selects the most recent version on the main branch to appear in the view.

In addition, a /main/LATEST rule is required to create new elements in a view. If you create a new element when this rule is omitted, your view does not select that element. (Creating an element involves creating a main branch and an empty version, /main/0.)