logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

delta.1p (10044B)


  1. '\" et
  2. .TH DELTA "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. delta
  12. \(em make a delta (change) to an SCCS file (\fBDEVELOPMENT\fP)
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. delta \fB[\fR-nps\fB] [\fR-g \fIlist\fB] [\fR-m \fImrlist\fB] [\fR-r \fISID\fB] [\fR-y\fB[\fIcomment\fB]] \fIfile\fR...
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR delta
  21. utility shall be used to permanently introduce into the named SCCS
  22. files changes that were made to the files retrieved by
  23. .IR get
  24. (called the
  25. .IR g-files ,
  26. or generated files).
  27. .SH OPTIONS
  28. The
  29. .IR delta
  30. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  31. .IR "Section 12.2" ", " "Utility Syntax Guidelines",
  32. except that the
  33. .BR \-y
  34. option has an optional option-argument. This optional option-argument
  35. shall not be presented as a separate argument.
  36. .P
  37. The following options shall be supported:
  38. .IP "\fB\-r\ \fISID\fR" 10
  39. Uniquely identify which delta is to be made to the SCCS file. The use
  40. of this option shall be necessary only if two or more outstanding
  41. .IR get
  42. commands for editing (\c
  43. .IR get
  44. .BR \-e )
  45. on the same SCCS file were done by the same person (login name). The
  46. SID value specified with the
  47. .BR \-r
  48. option can be either the SID specified on the
  49. .IR get
  50. command line or the SID to be made as reported by the
  51. .IR get
  52. utility; see
  53. .IR "\fIget\fR\^".
  54. .IP "\fB\-s\fP" 10
  55. Suppress the report to standard output of the activity associated with
  56. each
  57. .IR file .
  58. See the STDOUT section.
  59. .IP "\fB\-n\fP" 10
  60. Specify retention of the edited
  61. .IR g-file
  62. (normally removed at completion of delta processing).
  63. .IP "\fB\-g\ \fIlist\fR" 10
  64. Specify a
  65. .IR list
  66. (see
  67. .IR "\fIget\fR\^"
  68. for the definition of
  69. .IR list )
  70. of deltas that shall be ignored when the file is accessed at the
  71. change level (SID) created by this delta.
  72. .IP "\fB\-m\ \fImrlist\fR" 10
  73. Specify a modification request (MR) number that the application shall
  74. supply as the reason for creating the new delta. This shall be used if
  75. the SCCS file has the
  76. .BR v
  77. flag set; see
  78. .IR "\fIadmin\fR\^".
  79. .RS 10
  80. .P
  81. If
  82. .BR \-m
  83. is not used and
  84. .BR '\-'
  85. is not specified as a file argument, and the standard input is a
  86. terminal, the prompt described in the STDOUT section shall be written
  87. to standard output before the standard input is read; if the standard
  88. input is not a terminal, no prompt shall be issued.
  89. .P
  90. MRs in a list shall be separated by
  91. <blank>
  92. characters or escaped
  93. <newline>
  94. characters. An unescaped
  95. <newline>
  96. shall terminate the MR list. The escape character is
  97. <backslash>.
  98. .P
  99. If the
  100. .BR v
  101. flag has a value, it shall be taken to be the name of a program which
  102. validates the correctness of the MR numbers. If a non-zero exit status
  103. is returned from the MR number validation program, the
  104. .IR delta
  105. utility shall terminate. (It is assumed that the MR numbers were not
  106. all valid.)
  107. .RE
  108. .IP "\fB\-y\fB[\fIcomment\fB]\fR" 10
  109. Describe the reason for making the delta. The
  110. .IR comment
  111. shall be an arbitrary group of lines that would meet the definition of
  112. a text file. Implementations shall support
  113. .IR comment s
  114. from zero to 512 bytes and may support longer values. A null string
  115. (specified as either
  116. .BR \-y ,
  117. .BR \-y \c
  118. .BR \(dq\^\(dq ,
  119. or in response to a prompt for a comment) shall be considered a valid
  120. .IR comment .
  121. .RS 10
  122. .P
  123. If
  124. .BR \-y
  125. is not specified and
  126. .BR '\-'
  127. is not specified as a file argument, and the standard input is a
  128. terminal, the prompt described in the STDOUT section shall be written
  129. to standard output before the standard input is read; if the standard
  130. input is not a terminal, no prompt shall be issued. An unescaped
  131. <newline>
  132. shall terminate the comment text. The escape character is
  133. <backslash>.
  134. .P
  135. The
  136. .BR \-y
  137. option shall be required if the
  138. .IR file
  139. operand is specified as
  140. .BR '\-' .
  141. .RE
  142. .IP "\fB\-p\fP" 10
  143. Write (to standard output) the SCCS file differences before and after
  144. the delta is applied in
  145. .IR diff
  146. format; see
  147. .IR "\fIdiff\fR\^".
  148. .SH OPERANDS
  149. The following operand shall be supported:
  150. .IP "\fIfile\fR" 10
  151. A pathname of an existing SCCS file or a directory. If
  152. .IR file
  153. is a directory, the
  154. .IR delta
  155. utility shall behave as though each file in the directory were
  156. specified as a named file, except that non-SCCS files (last component
  157. of the pathname does not begin with
  158. .BR s. )
  159. and unreadable files shall be silently ignored.
  160. .RS 10
  161. .P
  162. If exactly one
  163. .IR file
  164. operand appears, and it is
  165. .BR '\-' ,
  166. the standard input shall be read; each line of the standard input shall
  167. be taken to be the name of an SCCS file to be processed. Non-SCCS files
  168. and unreadable files shall be silently ignored.
  169. .RE
  170. .SH STDIN
  171. The standard input shall be a text file used only in the following
  172. cases:
  173. .IP " *" 4
  174. To read an
  175. .IR mrlist
  176. or a
  177. .IR comment
  178. (see the
  179. .BR \-m
  180. and
  181. .BR \-y
  182. options).
  183. .IP " *" 4
  184. A
  185. .IR file
  186. operand shall be specified as
  187. .BR '\-' .
  188. In this case, the
  189. .BR \-y
  190. option must be used to specify the comment, and if the SCCS file has
  191. the
  192. .BR v
  193. flag set, the
  194. .BR \-m
  195. option must also be used to specify the MR list.
  196. .SH "INPUT FILES"
  197. Input files shall be text files whose data is to be included in the
  198. SCCS files. If the first character of any line of an input file is
  199. <SOH>
  200. in the POSIX locale, the results are unspecified. If this file contains
  201. more than 99\|999 lines, the number of lines recorded in the header for
  202. this file shall be 99\|999 for this delta.
  203. .SH "ENVIRONMENT VARIABLES"
  204. The following environment variables shall affect the execution of
  205. .IR delta :
  206. .IP "\fILANG\fP" 10
  207. Provide a default value for the internationalization variables that are
  208. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  209. .IR "Section 8.2" ", " "Internationalization Variables"
  210. for the precedence of internationalization variables used to determine
  211. the values of locale categories.)
  212. .IP "\fILC_ALL\fP" 10
  213. If set to a non-empty string value, override the values of all the
  214. other internationalization variables.
  215. .IP "\fILC_CTYPE\fP" 10
  216. Determine the locale for the interpretation of sequences of bytes of
  217. text data as characters (for example, single-byte as opposed to
  218. multi-byte characters in arguments and input files).
  219. .IP "\fILC_MESSAGES\fP" 10
  220. .br
  221. Determine the locale that should be used to affect the format and
  222. contents of diagnostic messages written to standard error, and
  223. informative messages written to standard output.
  224. .IP "\fINLSPATH\fP" 10
  225. Determine the location of message catalogs for the processing of
  226. .IR LC_MESSAGES .
  227. .IP "\fITZ\fP" 10
  228. Determine the timezone in which the time and date are written in the
  229. SCCS file. If the
  230. .IR TZ
  231. variable is unset or NULL, an unspecified system default timezone is
  232. used.
  233. .SH "ASYNCHRONOUS EVENTS"
  234. If SIGINT is caught, temporary files shall be cleaned up and
  235. .IR delta
  236. shall exit with a non-zero exit code. The standard action shall
  237. be taken for all other signals; see
  238. .IR "Section 1.4" ", " "Utility Description Defaults".
  239. .SH STDOUT
  240. The standard output shall be used only for the following messages in
  241. the POSIX locale:
  242. .IP " *" 4
  243. Prompts (see the
  244. .BR \-m
  245. and
  246. .BR \-y
  247. options) in the following formats:
  248. .RS 4
  249. .sp
  250. .RS 4
  251. .nf
  252. "MRs? "
  253. .P
  254. "comments? "
  255. .fi
  256. .P
  257. .RE
  258. .P
  259. The MR prompt, if written, shall always precede the comments prompt.
  260. .RE
  261. .IP " *" 4
  262. A report of each file's activities (unless the
  263. .BR \-s
  264. option is specified) in the following format:
  265. .RS 4
  266. .sp
  267. .RS 4
  268. .nf
  269. "%s\en%d inserted\en%d deleted\en%d unchanged\en", <\fINew SID\fR>,
  270. <\fInumber of lines inserted\fR>, <\fInumber of lines deleted\fR>,
  271. <\fInumber of lines unchanged\fR>
  272. .fi
  273. .P
  274. .RE
  275. .RE
  276. .SH STDERR
  277. The standard error shall be used only for diagnostic messages.
  278. .SH "OUTPUT FILES"
  279. Any SCCS files updated shall be files of an unspecified format.
  280. .SH "EXTENDED DESCRIPTION"
  281. .SS "System Date and Time"
  282. .P
  283. When a delta is added to an SCCS file, the system date and time shall
  284. be recorded for the new delta. If a
  285. .IR get
  286. is performed using an SCCS file with a date recorded apparently in the
  287. future, the behavior is unspecified.
  288. .SH "EXIT STATUS"
  289. The following exit values shall be returned:
  290. .IP "\00" 6
  291. Successful completion.
  292. .IP >0 6
  293. An error occurred.
  294. .SH "CONSEQUENCES OF ERRORS"
  295. Default.
  296. .LP
  297. .IR "The following sections are informative."
  298. .SH "APPLICATION USAGE"
  299. Problems can arise if the system date and time have been modified (for
  300. example, put forward and then back again, or unsynchronized clocks
  301. across a network) and can also arise when different values of the
  302. .IR TZ
  303. environment variable are used.
  304. .P
  305. Problems of a similar nature can also arise for the operation of the
  306. .IR get
  307. utility, which records the date and time in the file body.
  308. .SH EXAMPLES
  309. None.
  310. .SH RATIONALE
  311. None.
  312. .SH "FUTURE DIRECTIONS"
  313. None.
  314. .SH "SEE ALSO"
  315. .IR "Section 1.4" ", " "Utility Description Defaults",
  316. .IR "\fIadmin\fR\^",
  317. .IR "\fIdiff\fR\^",
  318. .IR "\fIget\fR\^",
  319. .IR "\fIprs\fR\^",
  320. .IR "\fIrmdel\fR\^"
  321. .P
  322. The Base Definitions volume of POSIX.1\(hy2017,
  323. .IR "Chapter 8" ", " "Environment Variables",
  324. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  325. .\"
  326. .SH COPYRIGHT
  327. Portions of this text are reprinted and reproduced in electronic form
  328. from IEEE Std 1003.1-2017, Standard for Information Technology
  329. -- Portable Operating System Interface (POSIX), The Open Group Base
  330. Specifications Issue 7, 2018 Edition,
  331. Copyright (C) 2018 by the Institute of
  332. Electrical and Electronics Engineers, Inc and The Open Group.
  333. In the event of any discrepancy between this version and the original IEEE and
  334. The Open Group Standard, the original IEEE and The Open Group Standard
  335. is the referee document. The original Standard can be obtained online at
  336. http://www.opengroup.org/unix/online.html .
  337. .PP
  338. Any typographical or formatting errors that appear
  339. in this page are most likely
  340. to have been introduced during the conversion of the source files to
  341. man page format. To report such errors, see
  342. https://www.kernel.org/doc/man-pages/reporting_bugs.html .