RMDEL(1POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

🌸 RMDEL(1POSIX) — the POSIX Programmer's Manual, bestie edition 🌸

okay so before we even get into it — hi, welcome to the POSIX Programmer's Manual 💖. This page is part of it. That's the manual name, consider it folded in, we're moving on.

⚠️ Real talk for two seconds: the Linux implementation of this interface may differ from what's written here (so like, go check the corresponding Linux manual page for the actual Linux behavior), or honestly the interface may not even be implemented on Linux at all. No cap. Check first. 💀

✨ NAME ✨

rmdel — remove a delta from an SCCS file. It's tagged (DEVELOPMENT) btw, which is giving "this is for the dev girlies" 💅

🎀 SYNOPSIS 🎀

rmdel -r SID file...

🦋 DESCRIPTION 🦋

So the rmdel utility shall remove the delta specified by the SID from each named SCCS file. And which delta is it removing, exactly? The delta to be removed shall be the most recent delta in its branch in the delta chain of each named SCCS file. That's the one. The most recent one on its branch. Periodt.

On top of that, the application shall ensure that the SID specified is not that of a version being edited for the purpose of making a delta. Translating: if a p-file exists for the named SCCS file (p-file, see get), then the SID you specified shall not appear in any entry of the p-file. Not one. 🙅‍♀️

Removal of a delta shall be restricted to:

  1. The user who made the delta
  2. The owner of the SCCS file
  3. The owner of the directory containing the SCCS file

If you're not one of those three, it's not your moment, bestie 😭

💅 OPTIONS 💅

The rmdel utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines. Yes, we follow the guidelines. We're nothing if not well-behaved.

The following option shall be supported:

  • -r SID — Specify the SCCS identification string (SID) of the delta to be deleted. That's the one, that's the only one, and it's kind of essential. 🔥

🌈 OPERANDS 🌈

The following operand shall be supported:

  • file — A pathname of an existing SCCS file or a directory. If file is a directory, the rmdel utility shall behave as though each file in the directory were specified as a named file — EXCEPT that non-SCCS files (meaning the last component of the pathname does not begin with s.) and unreadable files shall be silently ignored. Silently. No drama, no error message, they just get skipped. 🫶

And then: if exactly one file operand appears, and it is '-', the standard input shall be read; each line of the standard input is taken to be the name of an SCCS file to be processed. Non-SCCS files and unreadable files shall be silently ignored here too. Same energy. 💜

🍓 STDIN 🍓

The standard input shall be a text file used only when the file operand is specified as '-'. Each line of the text file shall be interpreted as an SCCS pathname. That's it, that's the whole vibe.

🧚 INPUT FILES 🧚

The SCCS files shall be files of unspecified format. Mystery format. We don't ask, we don't tell. 🙈

💜 ENVIRONMENT VARIABLES 💜

The following environment variables shall affect the execution of rmdel:

  • LANG — Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) The fallback queen. 👑
  • LC_ALL — If set to a non-empty string value, override the values of all the other internationalization variables. She overrides. That's her job. 💅
  • LC_CTYPE — Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files). Character interpretation business.
  • LC_MESSAGES — Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error. She styles your error messages. ✨
  • NLSPATH — Determine the location of message catalogs for the processing of LC_MESSAGES. Where the message catalogs live, basically. 🏠

⭐ ASYNCHRONOUS EVENTS ⭐

Default. Nothing special, we're chill about it.

🌸 STDOUT 🌸

Not used. She's not speaking. 🤐

💀 STDERR 💀

The standard error shall be used only for diagnostic messages. Only. Diagnostics. That's her one job.

👑 OUTPUT FILES 👑

The SCCS files shall be files of unspecified format (again — mystery format, we don't peek 🙈). During processing of a file, a temporary x-file, as described in admin, may be created and deleted; a locking z-file, as described in get, may be created and deleted. Temporary little guys. They come, they go. 🦋

🎀 EXTENDED DESCRIPTION 🎀

None. Nothing more to say, she said what she said.

✨ EXIT STATUS ✨

The following exit values shall be returned:

  • 0 — Successful completion. Slay. 🎉
  • >0 — An error occurred. 😭

🔥 CONSEQUENCES OF ERRORS 🔥

Default.

The following sections are informative. (yes, we're in the informative zone now, keep scrolling bestie)

🫶 APPLICATION USAGE 🫶

None.

🌈 EXAMPLES 🌈

None.

💜 RATIONALE 💜

None.

⭐ FUTURE DIRECTIONS ⭐

None.

🦋 SEE ALSO 🦋

admin, delta, get, prs

The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

and that's the whole page, bestie 💖 this iconic little number is brought to you by IEEE/The Open Group, 2017 — mwah, go remove some deltas responsibly (only your own, or ones you own, you know the rules) 🎀✨

📦 where this page comes from