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-init(1) Schily´s USER COMMANDS sccs-init(1)

sccs-init - create a new SCCS repository in the given directory

sccs init [options] [directory1 .. directoryn]

The init subcommand creates a new SCCS repository in the given list of directories. If no directory argument is given, the current working directory is used.

This subcommand is a project extension that does not exist in historic sccs implementations.

-f
Force to initialize even if already initialized. This also permits to create a SCCS repositary insiden an existing repository.
-i
Select in tree mode for the SCCS history files. The history files are kept in a directory SCCS inside the directory where the g-files are located. The default is to create an off tree repository that keeps the history files in a shadow tree under .sccs/data.
-s
Create a new repository with separately managed files does not support project bundling.

To create a new SCCS repository in the current directory call:
sccs init .

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

SCCS_NO_HELP
If set, sccs init 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 Evolving

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-create(1), sccs-cvt(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-diffs(1), sccs-edit(1), sccs-editor(1), sccs-enter(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(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 init was originally written by Joerg Schilling in 2015 and is still 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/06/28 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.