sccs-init(1)

💖 sccs-init(1) — Schily´s USER COMMANDS 💖

okay so bestie, you found the init page from Schily´s USER COMMANDS, and it’s giving “fresh repo, fresh me” energy. ✨ This is where sccs init sets up a shiny new SCCS repository — no cap.

🌸 NAME 🌸

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

✨ SYNOPSIS ✨

sccs init [options] [directory1 .. directoryn]

🦋 DESCRIPTION 🦋

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. iykyk — it’s a glow-up, not a blast from the past.

🎀 OPTIONS 🎀

• -f — Force initialization even if already initialized. This also permits one to create a SCCS repository inside an existing repository. bold move, bestie.
• -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 — this does not support project bundling.

🔥 EXAMPLES 🔥

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

sccs init .

🌈 ENVIRONMENT VARIABLES 🌈

See environ(7) 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.

👑 ATTRIBUTES 👑

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

• Availability — SCHILYdeveloper-build-sccs
• Interface Stability — Evolving

💜 SEE ALSO 💜

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(5), sccsfile(5).

💀 BUGS 💀

None currently known. 😌

Mail bugs and suggestions to schilytools@mlists.in-berlin.de or open a ticket at https://codeberg.org/schilytools/schilytools/issues.

The mailing list archive may be found at:

https://mlists.in-berlin.de/mailman/listinfo/schilytools-mlists.in-berlin.de.

🫶 AUTHOR 🫶

sccs init was originally written by Joerg Schilling in 2015 and is now maintained by the schilytools project authors. 👑

⭐ SOURCE DOWNLOAD ⭐

The source code for SCCS is included in the schilytools project and may be retrieved from the schilytools project at Codeberg at

https://codeberg.org/schilytools/schilytools.

The download directory is

https://codeberg.org/schilytools/schilytools/releases.

---

💌 source/version: schilytools · date: 2022/10/06 · author: Joerg Schilling · page: sccs-init(1) — mwah! 💌