[Chapter 17] 17.2 Basic Operation
Author: Daniel Gilly & the Staff of O'Reilly & Associates
Date: 1998-08-06T22:01:46Z

#

| Chapter 17 The SCCS Utility |

## 17.2 Basic Operation

This subsection outlines the steps to follow when using SCCS:

- Creating an SCCS file

- Retrieving a file

- Creating new releases and branches

- Recording changes

### 17.2.1 Creating an SCCS File

The admin command with the -i option creates and initializes SCCS files. For example:

>     admin -ich01 s.ch01

creates a new SCCS file and initializes it with the contents of ch01, which will become `delta 1.1`. The message, "No id keywords (cm7)" appears if you do not specify any keywords. In general, "id keywords" refer to variables in the files that are replaced with appropriate values by get, identifying the date and time of creation, the version retrieved, etc. A listing of identification keywords occurs later in this section.

Once the s.ch01 file is created, the original file ch01 can be removed, since it can be easily regenerated with the get command.

### 17.2.2 Retrieving a File

The get command can retrieve any version of a file from SCCS. Using the example above, you can retrieve ch01 by entering:

>     get -e s.ch01

and the messages:

>     1.1
>     new delta 1.2
>     272 lines

may appear. This indicates that you are "getting" `delta 1.1`, and the resulting file has 272 lines of text. When the file is reentered into the SCCS file s.ch01 with the delta command, its changes are `delta 1.2`.

The -e option indicates to SCCS that you intend to make more changes to the file and then reenter it into SCCS. Without this option, you will receive the file with read-only permissions. The -e option, besides releasing the file with read-write permissions, also creates a file p.ch01, which records information that will be used by SCCS when the file is returned.

### 17.2.3 Creating New Releases and Branches

The -r option to get tells SCCS what release and level number you want, but if no level is specified it defaults to the highest level available. With the command:

>     get -r3.2 ch01

delta 3.2 will be the release. However, the command:

>     get -r3 ch01

returns the highest-numbered level in release 3, for example 3.8. With the -r option omitted, get defaults to the highest release, highest level - in other words, the latest version.

When major changes are in store for a file, you may want to begin a new release of the file. You can do that by "getting" the file with the next highest release number. For example, if the latest release of a file is 3.2, and you want to start release 4, enter:

>     get -e -r4 ch01

You will receive the message:

>     3.2
>     new delta 4.1
>     53 lines

If you want to make a change to an older version of the same file, you can enter:

>     get -e -r2.2 ch01

and receive the message:

>     2.2
>     new delta 2.2.1.1
>     121 lines

You have now created a new branch from the trunk, stemming from version 2.2. Changes in this delta will not affect those in the trunk deltas, i.e., 2.3, 3.1, etc.

### 17.2.4 Recording Changes

Once changes have been made to the SCCS file, return it to SCCS with the command:

>     delta s.ch01

You are prompted for comments on the changes. The delta command then does its own get and uses diff to compare the new version of the file with the most recent version. It then prints messages giving the new release number and the number of lines that were inserted, deleted, and unchanged.

17.1 Overview of Commands |  | 17.3 Identification Keywords