GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
sccs-create(1) Schily´s USER COMMANDS sccs-create(1)

sccs-create, sccs-enter - create (initialize) history files

sccs create [options] [file1 .. filen]
sccs enter [options] [file1 .. filen]

The create subcommand creates an 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.

sccs create performs the following steps:

o
Creates the history file called s.program.c in the SCCS subdirectory.
o
Renames the original source file to ,program.c in the current directory.
o
Performs an `sccs get' on program.c to retrieve a read-only copy of the initial version.

The enter subcommand is similar to the sccs create command, but it omits the final `sccs get'. This can be used if an `sccs edit' is to be performed immediately after the history file is initialized.

Options are passed to the admin program, e.g.:
-o
Use the original file time instead of the current time for the time of the initial delta.

To create a new SCCS repository for the file xec.c in the current directory call:
sccs create xec.c

See environ(5) for descriptions of the following environment variables that affect the execution of sccs-create(1): LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.

SCCS_NO_HELP
If set, sccs create will not automatically call help(1) with the SCCS error code in order to print a more helpful error message. Scripts that depend on the exact error messages of SCCS commands should set the environment variable SCCS_NO_HELP and set LC_ALL=C.

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE
Availability SCHILYdeveloper-build-sccs
Interface Stability Committed

sccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(1), sccs-clean(1), sccs-comb(1), sccs-commit(1), sccs-cvt(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-diffs(1), sccs-edit(1), sccs-editor(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(1), sccs-init(1), sccs-istext(1), sccs-ldiffs(1), sccs-log(1), sccs-print(1), sccs-prs(1), sccs-prt(1), sccs-rcs2sccs(1), sccs-remove(1), sccs-rename(1), sccs-rmdel(1), sccs-root(1), sccs-sact(1), sccs-sccsdiff(1), sccs-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), what(1), sccschangeset(4), sccsfile(4).

sccs create was originally written by Eric Allman at UCB in 1980. It was later maintained by various people at AT&T and Sun Microsystems. Since 2006, it is maintained by Joerg Schilling.

A frequently updated source code for the SCCS suite is included in the schilytools project and may be retrieved from the schilytools project at Sourceforge at:

http://sourceforge.net/projects/schilytools/

The download directory is:

http://sourceforge.net/projects/schilytools/files/

Check for the schily-*.tar.bz2 archives.

Less frequently updated source code for the SCCS suite is at:

http://sourceforge.net/projects/sccs/files/

Separate project informations for the SCCS project may be retrieved from:

http://sccs.sf.net

2020/07/05 Joerg Schilling

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.