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