1DELTA(P) POSIX Programmer's Manual DELTA(P)
2
6 delta - make a delta (change) to an SCCS file (DEVELOPMENT)
7
9 delta [-nps][-g list][-m mrlist][-r SID][-y[comment]] file...
10
12 The delta utility shall be used to permanently introduce into the named
13 SCCS files changes that were made to the files retrieved by get (called
14 the g-files, or generated files).
15
17 The delta utility shall conform to the Base Definitions volume of
18 IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines, except
19 that the -y option has an optional option-argument. This optional
20 option-argument shall not be presented as a separate argument.
21 The following options shall be supported:
23 -r SID
25 Uniquely identify which delta is to be made to the SCCS file.
26 The use of this option shall be necessary only if two or more
27 outstanding get commands for editing ( get -e) on the same SCCS
28 file were done by the same person (login name). The SID value
29 specified with the -r option can be either the SID specified on
30 the get command line or the SID to be made as reported by the
31 get utility; see get .
32 -s Suppress the report to standard output of the activity associ‐
34 ated with each file. See the STDOUT section.
35 -n Specify retention of the edited g-file (normally removed at com‐
37 pletion of delta processing).
38 -g list
40 Specify a list (see get for the definition of list) of deltas
41 that shall be ignored when the file is accessed at the change
42 level (SID) created by this delta.
43 -m mrlist
45 Specify a modification request (MR) number that the application
46 shall supply as the reason for creating the new delta. This
47 shall be used if the SCCS file has the v flag set; see admin .
48 If -m is not used and '-' is not specified as a file argument, and the
50 standard input is a terminal, the prompt described in the STDOUT sec‐
51 tion shall be written to standard output before the standard input is
52 read; if the standard input is not a terminal, no prompt shall be
53 issued.
54 MRs in a list shall be separated by <blank>s or escaped <newline>s. An
56 unescaped <newline> shall terminate the MR list. The escape character
57 is <backslash>.
58 If the v flag has a value, it shall be taken to be the name of a pro‐
60 gram which validates the correctness of the MR numbers. If a non-zero
61 exit status is returned from the MR number validation program, the
62 delta utility shall terminate. (It is assumed that the MR numbers were
63 not all valid.)
64 -y[comment]
66 Describe the reason for making the delta. The comment shall be
67 an arbitrary group of lines that would meet the definition of a
68 text file. Implementations shall support comments from zero to
69 512 bytes and may support longer values. A null string (speci‐
70 fied as either -y, -y "" , or in response to a prompt for a com‐
71 ment) shall be considered a valid comment.
72 If -y is not specified and '-' is not specified as a file argument, and
74 the standard input is a terminal, the prompt described in the STDOUT
75 section shall be written to standard output before the standard input
76 is read; if the standard input is not a terminal, no prompt shall be
77 issued. An unescaped <newline> shall terminate the comment text. The
78 escape character is <backslash>.
79 The -y option shall be required if the file operand is specified as '-'
81 .
82 -p Write (to standard output) the SCCS file differences before and
84 after the delta is applied in diff format; see diff .
85
88 The following operand shall be supported:
89 file A pathname of an existing SCCS file or a directory. If file is a
91 directory, the delta utility shall behave as though each file in
92 the directory were specified as a named file, except that non-
93 SCCS files (last component of the pathname does not begin with
94 s.) and unreadable files shall be silently ignored.
95 If exactly one file operand appears, and it is '-' , the standard input
97 shall be read; each line of the standard input shall be taken to be the
98 name of an SCCS file to be processed. Non-SCCS files and unreadable
99 files shall be silently ignored.
100
103 The standard input shall be a text file used only in the following
104 cases:
105 * To read an mrlist or a comment (see the -m and -y options).
107 * A file operand shall be specified as '-' . In this case, the -y
109 option must be used to specify the comment, and if the SCCS file has
110 the v flag set, the -m option must also be used to specify the MR
111 list.
112
114 Input files shall be text files whose data is to be included in the
115 SCCS files. If the first character of any line of an input file is
116 <SOH> in the POSIX locale, the results are unspecified. If this file
117 contains more than 99999 lines, the number of lines recorded in the
118 header for this file shall be 99999 for this delta.
119
121 The following environment variables shall affect the execution of
122 delta:
123 LANG Provide a default value for the internationalization variables
125 that are unset or null. (See the Base Definitions volume of
126 IEEE Std 1003.1-2001, Section 8.2, Internationalization Vari‐
127 ables for the precedence of internationalization variables used
128 to determine the values of locale categories.)
129 LC_ALL If set to a non-empty string value, override the values of all
131 the other internationalization variables.
132 LC_CTYPE
134 Determine the locale for the interpretation of sequences of
135 bytes of text data as characters (for example, single-byte as
136 opposed to multi-byte characters in arguments and input files).
137 LC_MESSAGES
139 Determine the locale that should be used to affect the format
140 and contents of diagnostic messages written to standard error,
141 and informative messages written to standard output.
142 NLSPATH
144 Determine the location of message catalogs for the processing of
145 LC_MESSAGES .
146 TZ Determine the timezone in which the time and date are written in
148 the SCCS file. If the TZ variable is unset or NULL, an unspeci‐
149 fied system default timezone is used.
150
153 If SIGINT is caught, temporary files shall be cleaned up and delta
154 shall exit with a non-zero exit code. The standard action shall be
155 taken for all other signals; see Utility Description Defaults .
156
158 The standard output shall be used only for the following messages in
159 the POSIX locale:
160 * Prompts (see the -m and -y options) in the following formats:
162 "MRs? "
165 "comments? "
168 The MR prompt, if written, shall always precede the comments prompt.
170 * A report of each file's activities (unless the -s option is speci‐
172 fied) in the following format:
173 "%s\n%d inserted\n%d deleted\n%d unchanged\n", <New SID>,
176 <number of lines inserted>, <number of lines deleted>,
177 <number of lines unchanged>
178
180 The standard error shall be used only for diagnostic messages.
181
183 Any SCCS files updated shall be files of an unspecified format.
184
186 System Date and Time
187 When a delta is added to an SCCS file, the system date and time shall
188 be recorded for the new delta. If a get is performed using an SCCS file
189 with a date recorded apparently in the future, the behavior is unspeci‐
190 fied.
191
193 The following exit values shall be returned:
194 0 Successful completion.
196 >0 An error occurred.
198
201 Default.
202 The following sections are informative.
204
206 Problems can arise if the system date and time have been modified (for
207 example, put forward and then back again, or unsynchronized clocks
208 across a network) and can also arise when different values of the TZ
209 environment variable are used.
210 Problems of a similar nature can also arise for the operation of the
212 get utility, which records the date and time in the file body.
213
215 None.
216
218 None.
219
221 None.
222
224 Utility Description Defaults , admin , diff , get , prs , rmdel
225
227 Portions of this text are reprinted and reproduced in electronic form
228 from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
229 -- Portable Operating System Interface (POSIX), The Open Group Base
230 Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
231 Electrical and Electronics Engineers, Inc and The Open Group. In the
232 event of any discrepancy between this version and the original IEEE and
233 The Open Group Standard, the original IEEE and The Open Group Standard
234 is the referee document. The original Standard can be obtained online
235 at http://www.opengroup.org/unix/online.html .
236IEEE/The Open Group 2003 DELTA(P)