sccs-create(1)

📦 version 2022.10.16, in opensuse-leap 16.0

💅 sccs-create(1) — Schily´s USER COMMANDS ✨

okay so bestie, welcome to sccs-create(1) — the page where we initialize history files and make it look effortless 🎀

🌸 NAME 🌸

sccs-create, sccs-enter — create (initialize) history files. that's the whole vibe, we're birthing history files today 👑

✨ SYNOPSIS ✨

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

🦋 DESCRIPTION 🦋

so the create subcommand creates an SCCS file, and it takes the initial contents from the file of the same name. no cap, that's it. any flags to admin are accepted, she's flexible like that 💅

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 — like, once you're sure, go ahead and yeet them 🧹

sccs create performs the following steps:

  • creates the history file called s.program.c in the SCCS subdirectory 📁
  • renames the original source file to ,program.c in the current directory
  • 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. use it when an sccs edit is gonna be performed immediately after the history file is initialized — main character efficiency fr fr 🚀

💖 OPTIONS 💖

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 ⏰

🌈 EXAMPLES 🌈

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

sccs create xec.c

slay. that's it. go off ✨

🍓 ENVIRONMENT VARIABLES 🍓

see environ(7) 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 🫶
ngl if you're scripting, this one matters — set SCCS_NO_HELP and LC_ALL=C together or your error matching is gonna be a whole mess 😭

🧚 ATTRIBUTES 🧚

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

  • Attribute Type: Availability — Attribute Value: SCHILYdeveloper-build-sccs
  • Attribute Type: Interface Stability — Attribute Value: Committed

(ok yes this was a table in the original, but tables don't render here so we're doing bullets, it's giving adapt-and-overcome 💅)

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

that's the whole friend group, iykyk 🫶

💀 BUGS 💀

none currently known. literally flawless, we love to see it 💅

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 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 has been maintained by Joerg Schilling and the schilytools project authors. iconic lineage honestly 🎀

🎀 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.

and that's the page bestie 🦋 this was Joerg Schilling, 2022/10/06 — go forth, make history files, and remember to clean up those comma files 💖✨

📦 where this page comes from