sccs-sccsdiff(1)

📦 version 2022.10.16, in opensuse-leap 16.0

💅 sccs-sccsdiff — comparing two versions of an SCCS file (yes bestie, it's a diff tool)

Okay so this is sccs-sccsdiff (and its alias sccsdiff), living its best life in section 1 of the manual. The whole personality? It compares two versions of an SCCS file and shows you the differences. That's it, that's the vibe. 🎀

✨ SYNOPSIS ✨

/usr/ccs/bin/sccsdiff [-p] -rsid -rsid [diff-options]
    [-Nbulk-spec] s.filename

🌸 DESCRIPTION 🌸

So sccsdiff takes two versions of an SCCS file, puts them side by side (metaphorically, this is a terminal bestie), and displays the differences between them. Iconic behavior, honestly.

You can throw any number of SCCS files at it — like, go off. 💖 And heads up: the options you specify apply to all the named s.files. Every single one. No favorites.

🦋 OPTIONS 🦋

The following options are supported:

  • -p — pipes the output for each file through pr(1). Fancy formatting moment ✨
  • -rsid — picks a version corresponding to the indicated SCCS delta ID (SID) for the comparison. And the way versions get passed to diff(1)? In the order you gave them, bestie. Order matters, no cap. 🫶
  • diff-options — passes options straight through to diff(1), including: -b, -c, -e, -f, -h, -u, -C number, -U number, and -D string.
  • -Nbulk-spec — processes a bulk of SCCS history files. Literally the mass-processing option, it lets you do efficient mass processing of SCCS history files. Main character energy for your whole repo. 👑

The bulk-spec parameter is composed from an optional list of flag parameters followed by an optional path specifier.

The following flag types are supported:

  • none

The following path specifier types are supported:

  • -N — the file name parameters to the sccsdiff command are not s.filename files but the names of the g-files. The s.filename names are automatically derived from the g-file names by prepending s. to the last path name component. Both, s.filename and the g-file, are in the same directory. 🗂️
  • -Ns. — the file name parameters to the sccsdiff command are s.filename files. The g-files names are automatically derived by removing s. from the beginning of the last path name component of the s.filename. Both, s.filename and the g-file, are in the same directory.
  • -Ndir — the file name parameters to the sccsdiff command are not s.filename files but the names of the g-files. The s.filename names are put into directory dir, and the names are automatically derived from the g-file names by prepending dir/s. to the last path name component.
  • -Ndir/s. — the file name parameters to the sccsdiff command are s.filename files in directory dir. The g-files names are automatically derived by removing dir/s. from the beginning of the last path name component of the s.filename.

A typical value for dir is SCCS. Noted, bookmarking that. 📌

In order to overcome the limited number of exec(2) arguments, it is recommended to use − as the file name parameter for sccsdiff(1) and to send a list of path names to stdin.

This option is a SCHILY extension that does not exist in historic sccs implementations. So like, don't go looking for it in ye olde manuals. 🙈

  • -V, -version, --version — prints the sccsdiff version number string and exits. (The original literally says "and exists" — we respect the typo energy, but like, you know what it means bestie.)

This option is a SCHILY extension that does not exist in historic sccs implementations. 💅

🌈 ENVIRONMENT VARIABLES 🌈

See environ(7) for descriptions of the following environment variables that affect the execution of sccsdiff(1): LANG, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH.

  • SCCS_NO_HELP — if set, sccsdiff(1) 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. Fr fr, if your script is finicky about exact strings, do this. 😭

🍓 FILES 🍓

  • /tmp/get????? — temporary files. Living in /tmp, as one does. ⭐

👑 ATTRIBUTES 👑

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

  • Availability: SUNWsprot

💜 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-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-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), bdiff(1), diff(1), what(1), sccschangeset(5), sccsfile(5), attributes(7), environ(7), standards(7).

That's the whole friend group, go say hi. 🫶

🧚 DIAGNOSTICS 🧚

  • filename: No differences — if the two versions are the same. Literally identical, nothing to see, no drama. 💀

Use the SCCS help command for explanations of other messages. See sccs-help(1).

🔥 BUGS 🔥

None currently known. Clean slate, slay. ✨

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.

🌸 AUTHORS 🌸

The SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972. Release 4.0 of SCCS — which introduced new versions of the programs admin(1), get(1), prt(1), and delta(1) — was published on February 18, 1977; it introduced the new text based SCCS v4 history file format (previous SCCS releases used a binary history file format). The SCCS suite was later maintained by various people at AT&T and Sun Microsystems. Since 2006, the SCCS suite has been maintained by Joerg Schilling and the schilytools project authors. A whole 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 one shipped as part of SunOS 5.11, dated 2022/10/06 — go forth and diff those SCCS files, you've got this. 💅✨
📦 where this page comes from