sccs.html

IEEE 1003.1-2003, Single Unix Specification v3

If the <b>-b</b> option is given, branches shall be ignored in the determination of whether they are being edited; this is
dangerous if branches are kept in the same directory.</dd>

<dt><b>create</b></dt>

<dd>Create an SCCS file, taking the initial contents from the file of the same name. Any options to <a href=
"../utilities/admin.html"><i>admin</i></a> are accepted. If the creation is successful, the original files shall be renamed by
prefixing the basenames with a comma. These renamed files should be removed after it has been verified that the SCCS files have
been created successfully.</dd>

<dt><b>delget</b></dt>

<dd>Perform a <a href="../utilities/delta.html"><i>delta</i></a> on the named files and then <a href=
"../utilities/get.html"><i>get</i></a> new versions. The new versions shall have ID keywords expanded and shall not be editable.
Any <b>-m</b>, <b>-p</b>, <b>-r</b>, <b>-s</b>, and <b>-y</b> options shall be passed to <a href=
"../utilities/delta.html"><i>delta</i></a>, and any <b>-b</b>, <b>-c</b>, <b>-e</b>, <b>-i</b>, <b>-k</b>, <b>-l</b>, <b>-s</b>,
and <b>-x</b> options shall be passed to <a href="../utilities/get.html"><i>get</i></a>.</dd>

<dt><b>deledit</b></dt>

<dd>Equivalent to <b>delget</b>, except that the <a href="../utilities/get.html"><i>get</i></a> phase shall include the <b>-e</b>
option. This option is useful for making a checkpoint of the current editing phase. The same options shall be passed to <a href=
"../utilities/delta.html"><i>delta</i></a> as described above, and all the options listed for <a href=
"../utilities/get.html"><i>get</i></a> above except <b>-e</b> shall be passed to <b>edit</b>.</dd>

<dt><b>diffs</b></dt>

<dd>Write a difference listing between the current version of the files checked out for editing and the versions in SCCS format.
Any <b>-r</b>, <b>-c</b>, <b>-i</b>, <b>-x</b>, and <b>-t</b> options shall be passed to <a href=
"../utilities/get.html"><i>get</i></a>; any <b>-l</b>, <b>-s</b>, <b>-e</b>, <b>-f</b>, <b>-h</b>, and <b>-b</b> options shall be
passed to <a href="../utilities/diff.html"><i>diff</i></a>. A <b>-C</b> option shall be passed to <a href=
"../utilities/diff.html"><i>diff</i></a> as <b>-c</b>.</dd>

<dt><b>edit</b></dt>

<dd>Equivalent to <a href="../utilities/get.html"><i>get</i></a> <b>-e</b>.</dd>

<dt><b>fix</b></dt>

<dd>Remove the named delta, but leave a copy of the delta with the changes that were in it. It is useful for fixing small compiler
bugs, and so on. The application shall ensure that it is followed by a <b>-r</b> <i>SID</i> option. Since <b>fix</b> does not leave
audit trails, it should be used carefully.</dd>

<dt><b>info</b></dt>

<dd>Write a listing of all files being edited. If the <b>-b</b> option is given, branches (that is, SIDs with two or fewer
components) shall be ignored. If a <b>-u</b> <i>user</i> option is given, then only files being edited by the named user shall be
listed. A <b>-U</b> option shall be equivalent to <b>-u</b>&lt; <i>current&nbsp;user</i>&gt;.</dd>

<dt><b>print</b></dt>

<dd>Write out verbose information about the named files, equivalent to <i>sccs</i> <a href=
"../utilities/prs.html"><i>prs</i></a>.</dd>

<dt><b>tell</b></dt>

<dd>Write a &lt;newline&gt;-separated list of the files being edited to standard output. Takes the <b>-b</b>, <b>-u</b>, and
<b>-U</b> options like <b>info</b> and <b>check</b>.</dd>

<dt><b>unedit</b></dt>

<dd>This is the opposite of an <b>edit</b> or a <a href="../utilities/get.html"><i>get</i></a> <b>-e</b>. It should be used with
caution, since any changes made since the <a href="../utilities/get.html"><i>get</i></a> are lost.</dd>
</dl>
</blockquote>

<h4><a name="tag_04_125_14"></a>EXIT STATUS</h4>

<blockquote>
<p>The following exit values shall be returned:</p>

<dl compact>
<dt>&nbsp;0</dt>

<dd>Successful completion.</dd>

<dt>&gt;0</dt>

<dd>An error occurred.</dd>
</dl>
</blockquote>

<h4><a name="tag_04_125_15"></a>CONSEQUENCES OF ERRORS</h4>

<blockquote>
<p>Default.</p>
</blockquote>

<hr>
<div class="box"><em>The following sections are informative.</em></div>

<h4><a name="tag_04_125_16"></a>APPLICATION USAGE</h4>

<blockquote>
<p>Many of the SCCS utilities take directory names as operands as well as specific filenames. The pseudo-utilities supported by
<i>sccs</i> are not described as having this capability, but are not prohibited from doing so.</p>
</blockquote>

<h4><a name="tag_04_125_17"></a>EXAMPLES</h4>

<blockquote>
<ol>
<li>
<p>To get a file for editing, edit it and produce a new delta:</p>

<pre>
<tt>sccs get -e file.c
ex file.c
sccs delta file.c
</tt>
</pre>
</li>

<li>
<p>To get a file from another directory:</p>

<pre>
<tt>sccs -p /usr/src/sccs/s. get cc.c
</tt>
</pre>

<p>or:</p>

<pre>
<tt>sccs get /usr/src/sccs/s.cc.c
</tt>
</pre>
</li>

<li>
<p>To make a delta of a large number of files in the current directory:</p>

<pre>
<tt>sccs delta *.c
</tt>
</pre>
</li>

<li>
<p>To get a list of files being edited that are not on branches:</p>

<pre>
<tt>sccs info -b
</tt>
</pre>
</li>

<li>
<p>To delta everything being edited by the current user:</p>

<pre>
<tt>sccs delta $(sccs tell -U)
</tt>
</pre>
</li>

<li>
<p>In a makefile, to get source files from an SCCS file if it does not already exist:</p>

<pre>
<tt>SRCS = &lt;</tt><i>list of source files</i><tt>&gt;
$(SRCS):
    sccs get $(REL) $@
</tt>
</pre>
</li>
</ol>
</blockquote>

<h4><a name="tag_04_125_18"></a>RATIONALE</h4>

<blockquote>
<p>SCCS and its associated utilities are part of the XSI Development Utilities option within the XSI extension.</p>

<p>SCCS is an abbreviation for Source Code Control System. It is a maintenance and enhancement tracking tool. When a file is put
under SCCS, the source code control system maintains the file and, when changes are made, identifies and stores them in the file
with the original source code and/or documentation. As other changes are made, they too are identified and retained in the
file.</p>

<p>Retrieval of the original and any set of changes is possible. Any version of the file as it develops can be reconstructed for
inspection or additional modification. History data can be stored with each version, documenting why the changes were made, who
made them, and when they were made.</p>
</blockquote>

<h4><a name="tag_04_125_19"></a>FUTURE DIRECTIONS</h4>

<blockquote>
<p>None.</p>
</blockquote>

<h4><a name="tag_04_125_20"></a>SEE ALSO</h4>

<blockquote>
<p><a href="admin.html"><i>admin</i></a> , <a href="delta.html"><i>delta</i></a> , <a href="get.html"><i>get</i></a> , <a href=
"make.html"><i>make</i></a> , <a href="prs.html"><i>prs</i></a> , <a href="rmdel.html"><i>rmdel</i></a> , <a href=
"sact.html"><i>sact</i></a> , <a href="unget.html"><i>unget</i></a> , <a href="val.html"><i>val</i></a> , <a href=
"what.html"><i>what</i></a></p>
</blockquote>

<h4><a name="tag_04_125_21"></a>CHANGE HISTORY</h4>

<blockquote>
<p>First released in Issue 4.</p>
</blockquote>

<h4><a name="tag_04_125_22"></a>Issue 6</h4>

<blockquote>
<p>In the ENVIRONMENT VARIABLES section, the <i>PROJECTDIR</i> description is updated from &quot;otherwise, the home directory of a
user of that name is examined&quot; to &quot;otherwise, the value of <i>PROJECTDIR</i> is treated as a user name and that user's initial
working directory is examined&quot;.</p>

<p>The normative text is reworded to avoid use of the term &quot;must&quot; for application requirements.</p>
</blockquote>

<div class="box"><em>End of informative text.</em></div>

<hr>
<hr size="2" noshade>
<center><font size="2"><!--footer start-->
UNIX &reg; is a registered Trademark of The Open Group.<br>
POSIX &reg; is a registered Trademark of The IEEE.<br>
[ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
"../utilities/contents.html">XCU</a> | <a href="../functions/contents.html">XSH</a> | <a href="../xrat/contents.html">XRAT</a>
]</font></center>

<!--footer end-->
<hr size="2" noshade>
</body>
</html>