SCCS(1) | General Commands Manual | SCCS(1) |
sccs
— front end
for the SCCS
subsystem
sccs |
[-r ] [-d
path] [-T ]
[-V ] [--version ]
[-p path]
[--prefix=path] [--cssc ]
command [flags] [file
...] |
Sccs
is a front end to the
SCCS
programs that helps them mesh more cleanly with
the rest of UNIX. It also includes the capability to run “set user
id” to another user to provide additional protection (but see the
section entitled BUGS).
Basically, sccs
runs the command with the
specified flags and args. Each
argument is normally modified to be prepended with
“SCCS/s.
”.
Flags to be interpreted by the sccs
program must be before the command argument. Flags to
be passed to the actual SCCS
program must come after
the command argument. These flags are specific to the
command and are discussed in the documentation for that command.
Besides the usual SCCS
commands, several
“pseudo-commands” can be issued. These are:
edit
get -e
”.delget
-m
, -p
,
-r
, -s
, and
-y
flags will be passed to
delta
, and the -b,
-c
, -e
,
-i
, -k
,
-l
, -s
, and
-x
flags will be passed to get.deledit
delget
except that the
get
phase includes the -e
flag. This option is useful for making a
checkpoint
of your current editing phase. The same flags will be passed to delta as
described above, and all the flags listed for get
above except -e
and -k
are
passed to edit
.create
SCCS
file , taking the initial contents
from the file of the same name. Any flags to admin
are accepted. If the creation is successful, the files are renamed with a
comma on the front. These should be removed when you are convinced that
the SCCS
files have been created
successfully.fix
-r
flag. This command
essentially removes the named delta, but leaves you with a copy of the
delta with the changes that were in it. It is useful for fixing small
compiler bugs, etc. Since it doesn't leave audit trails, it should be used
carefully.clean
-b
flag is given, branches are ignored in the
determination of whether they are being edited; this is dangerous if you
are keeping the branches in the same directory.unedit
edit
or a
“get -e
”. It should be used with
extreme caution, since any changes you made since the get will be
irretrievably lost.info
-b
flag is given, branches (i.e.,
SID
´s with two or fewer components) are
ignored. If the -u
flag is given (with an optional
argument) then only files being edited by you (or the named user) are
listed.check
info
except that nothing is printed if
nothing is being edited, and a non-zero exit status is returned if
anything is being edited. The intent is to have this included in an
install
entry in a makefile to insure that everything is included into the
SCCS
file before a version is installed.tell
-b
and
-u
flags like info
and
check
.diffs
diff
listing between the current version
of the program(s) you have out for editing and the versions in
SCCS
format. The -r
,
-c
, -i
,
-x
, and -t
flags are
passed to
get
; the -l
,
-s
, -e
,
-f
, -h
,
-u
, -n
,
-w
, and -b
options are
passed to diff
. The -a
,
-B
, -d
,
-H
, -p
,
-q
, -s
,
-v
, and -y
options are
passed to diff
but these options are (usually)
specific to GNU diff, and so may not be supported on systems other than
GNU. The -C
flag is passed to
diff
as -c
.print
Certain commands (such as admin
) cannot be
run “set user id
” by all users, since
this would allow anyone to change the authorizations. These commands are
always run as the real user.
--cssc
--prefix
flag in order to find the
correct subprograms (non-GNU versions of sccs have the full pathnames for
the subprograms hard-coded). In this way, the CSSC test suite can be
compiled ready for installation in a particular directory, but the test
suite can still be run before the suite has been installed in its final
position. This option is supported only by the GNU version of
sccs
.--prefix=foo
-V
flag. This prefix is used without a final slash
being appended, so values like “/usr/local/bin/cssc-” can be
used. This option is disallowed if the program is installed setuid, and it
is supported only by the GNU version of sccs
.
This option is
not equivalent to the -p
flag.--version
-V
flag.-r
sccs
as the real user rather than as whatever
effective user sccs
is
“set user id
” to.-d
SCCS
files. The
default is the current directory. If environment variable
PROJECTDIR
is set, it will be used to determine
the -d
flag.-p
SCCS
files will be found;
“SCCS
” is the default. The
-p
flag differs from the
-d
flag in that the -d
argument is prepended to the entire pathname and the
-p
argument is inserted before the final component
of the pathname. For example, “sccs -d/x -py get
a/b
” will convert to “get
/x/a/y/s.b
”. The intent here is to create aliases such as
“alias syssccs sccs -d/usr/src
”
which will be used as “syssccs get
cmd/who.c
”.
Please note
that the -p
flag is (very)
different in purpose from the --prefix
option.-T
-V
sccs
program, and the subcommand prefix being used. This option is supported
only by the GNU version of sccs
.To get a file for editing, edit it, and produce a new delta:
sccs get -e file.c
ex file.c
sccs delta file.c
To get a file from another directory:
sccs -p/usr/src/sccs/s. get
cc.c
or
sccs get
/usr/src/sccs/s.cc.c
To make a delta of a large number of files in the current directory:
sccs delta *.c
To get a list of files being edited that are not on branches:
sccs info -b
To delta everything being edited by you:
sccs delta `sccs tell
-u`
In a makefile, to get source files from an
SCCS
file if it does not already exist:
SRCS = <list of source
files>
$(SRCS):
sccs get $(REL) $@
This version of sccs
is maintained by
James Youngman, <jay@gnu.org>.
PROJECTDIR
The PROJECTDIR environment variable is checked by the
-d
flag. If it begins with a slash, it is taken
directly; otherwise, the home directory of a user of that name is
examined for a subdirectory “src
”
or “source
”. If such a directory
is found, it is used.
There are many error messages, mostly brief but fairly obvious. If all goes acording to plan, the program's exit status is zero. Otherwise, it will be one of the following values:-
what(1), sccs-admin(1), sccs-cdc(1), sccs-comb(1), sccs-delta(1), sccs-get(1), sccs-help(1), sccs-prs(1), sccs-prt(1), sccs-rmchg(1), sccs-rmdel(1), sccs-sact(1), sccsdiff(1), sccs-unget(1), sccs-val(1), make(1), rcsintro(1), cvs(1), sccsfile(5).
Eric Allman, An Introduction to the Source Code Control System.
James Youngman, CSSC: Compatibly Stupid Source Control.
Copyright © 1998
Free Software Foundation, Inc. All rights reserved.
Copyright © 1983, 1990, 1993
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
This product includes software developed by the University of California, Berkeley and its contributors.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The sccs
command appeared in
4.3BSD.
This version of sccs
has been slightly
modified to support GNU Autoconf
, and several new
options (those beginning with two dashes and also
-V
) and to make it somewhat more portable. The
program otherwise remains largely unchanged.
It should be able to take directory arguments on pseudo-commands
like the SCCS
commands do.
Though this program is mostly derived from the original BSD code, the subprograms accompanying it in the CSSC suite (admin, get, delta and so on) are not the original AT&T code. Please do not count on these programs being secure.
Other known bugs are listed in the file BUGS, which accompanies GNU CSSC.
June 3, 1998 | GNU |