-
Notifications
You must be signed in to change notification settings - Fork 0
/
AN-2021-09-18
377 lines (270 loc) · 14.4 KB
/
AN-2021-09-18
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
New features with AN-2021-09-18:
This is the first localization step for the schily source consolidation. Many
programs now (hopefully) call gettext() for all strings that need localization.
- The next step will include dgettext() calls for the libraries and the
missing programs
- The following step will include the extracted strings
- The last step will include German translations and install support
for the resulting binary message object files.
----------> Please test and report compilation problems! <---------
***** NOTE: As mentioned since 2004, frontends to the tools should *****
***** call all programs in the "C" locale *****
***** by e.g. calling: LC_ALL=C cdrecord .... *****
***** unless these frontends support localized strings *****
***** used by the cdrtools with NLS support. *****
*** WARNING ***
*** Need new smake ***
*** Due to the fact that schily-tools 2014-04-03 introduced to use new macro
*** expansions and a related bug fix in smake, you need a newer smake
*** to compile this source. If your smake is too old and aborts, ensure to
*** use the recent smake by calling:
cd ./psmake
./MAKE-all
cd ..
psmake/smake
.... become "root" and then call:
psmake/smake install
The new smake version mentioned above is smake-1.2.4
The recent smake version is smake-1.5
*** Due to the fact that schily-tools 2018-01-26 introduced
*** optimizations for the Schily version of SunPro Make, you
*** need at least the dmake version from 2018/01/11 with support
*** for the "export" directive to compile with this makefile system.
For the beginning of the list of new features of the software in this tarball,
please scroll down to "NEW FEATURES"
WARNING: the new version of the isoinfo program makes use of the
*at() series of functions that have been introduced by Sun
in August 2001 and added to POSIX.1-2008. For older platforms,
libschily now includes emulations for these functions but
these emulations have not yet been tested thoroughly.
Please report problems!
BUG WARNING: Please never report bugs only to Linux distributions as
they usually do not forward these bug reports upstream and
the Linux distributions typically do not let skilled people
check the bugs. We did not hear about a FIFO problem in star
for a long time. Then a problem on Linux occurred once
every 6000-10000 tries but it did not happen on Solaris after
even 10 million tries, so it was not known besides Linux and
not reported to the project.
BUG WARNING: *** GNU make *** starts too early with parallel
execution (when reading Makefiles and evaluating rules for
"include" statements already). Since GNU make does not
support a concept for a correct ordering of such actions,
you need to be prepared to see GNU make fail in parallel
mode. If you try to compile a maiden unpacked schilytools
tarball in parallel mode using GNU make, this will definitely
fail as a result of the GNU make timestamp caching bug. See
below for more information.
If you are interested in reliable parallel execution,
it is recommended to use the included "dmake" program with
a command line like:
dmake -j10 -r -f SMakefile
from the top level directory. Note that if you are on Linux,
you need the dmake version from schilytools 2021-06-07 or
newer, since that version introduced a solution for a kernel
caused performance problem with filesystems on Linux. Older
dmake versions will not be faster in parallel mode on Linux.
The "dmake" program included in the schilytools tarball is the
current version of the "new" SunOS make program that has been
introduced in January 1986 by Sun Microsystems. It also
introduced new features (like the "include" directive) that
3 years later have been copied by gmake in a partially buggy
way. As gmake does not fix showstopper bugs, it cannot be
supported. Current showstoppers are: 1) gmake executes
"include" related rules in the inverse order, causing rules
to fail if they depend on files created by an "earlier" action
2) gmake caches an outdated state of the directory and aborts
with a wrong complain about allegedly missing files that in
fact exist already, because they just have been remade.
NEW FEATURES:
- smake: Fixed a typo in a comment in readfile.c
- smake: The man page now mentions that the commands called for
.INCLUDE_FAILED: should include $^ as argument to the rule command to
be able to know what filename is missing and to be pocessed.
- smake: Fix a bug in the man page for .INCLUDE_FAILED:. It now
correctly mentions that .INCLUDE_FAILED: only applies to the "include"
directive but not to the "-include" directive as well (as claimed
before).
- SunPro Make: The dynamic macro $^ is now documented in the man page.
It was always supported by SunPro Make, but for unknown reasons
undocumented in the official man page from Sun Microsystems.
- SunPro Make: The .INCLUDE_FAILED: special target is now supported
the same was as in smake.
History: smake introduced .INCLUDE_FAILED: 23 years ago (in July
1998) in order to be able to support completely unknown platforms with
the schily makefile system. This works fine, since a bootstrap smake
is compiled first in schilytools and this is done via a shell script.
That specific use case in smake (with a completely unknown platform,
based on an unknown operating system or an unknown CPU) will not work
with SunPro Make the same way, since SunPro Make needs smake as a
bootstrap make program for compilation. In other words, SunPro Make
is compiled on unknown platforms, using a bootstrap smake that was
compiled with a shell script and before SunPro Make is compiled on a
completely unknown platform, smake did already run the automake
scripts triggered from the .INCLUDE_FAILED: target while smake was
running.
Adding support for .INCLUDE_FAILED: to SunPro Make however still
makes sense, as support for .INCLUDE_FAILED: in SunPro Make allows to
automatically add initial basic support for new compilers to a
development tree using the schily makefile system or similar build
systems, while being on a platform with pre-existig SunPro Make
binaries. This may even be more probable than the case with a
completly unknown OS.
- SunPro Make: .INCLUDE_FAILED: special target 2nd group of changes:
.INCLUDE_FAILED: is no longer supported when make is in SVr4 mode
or when it is in compatibility mode to old SunPro Make versions.
.INCLUDE_FAILED: no longer permits dependencies to appear after the
colon. These dependencies have been previously ignored.
.INCLUDE_FAILED: is now better printed with make -p, since
.INCLUDE_FAILED: now appears in the first block of output that lists
.PHONY:, .PRECIOUS:, .SUFFIXES: as well.
- SunPro Make: A new section "Automake Features" has been added.
- SunPro Make: A new version date has been defined.
SCCS THOUGHTS:
- SCCS: The current idea for converting a historic SCCS project into
a project oriented SCCS history bundle is the following:
- Create a user map file for "sccslog" by calling:
mkdir $HOME/.sccs
$EDITOR $HOME/.sccs/usermap
Enter the UNIX login names followed by a TAB, followed
by an E-mail notation. Use one line per user, e.g.
joerg J. Schilling <[email protected]>
- Create a copy of the whole project to work on for this test.
Do not do this conversion on the original project until
sccs-6.0 is ready.
- chdir to the project home directory of the just created copy.
- Call "sccs init -i ." to make the project using an in-tree
project oriented repository.
- Call:
find * -path '*SCCS/s.*' | /opt/schily/ccs/bin/sccscvt -NSCCS/s. -k -ooo -V6 -
for the CSRG BSD project use:
find * -path '*SCCS/s.*' | TZ=US/Pacific /opt/schily/ccs/bin/sccscvt -NSCCS/s. -k -ooo -V6 -
to convert all history files into SCCSv6 history files. The
TZ=US/Pacific is important for the UCB conversion since SCCSv6
uses timezones but SCCSv4 does not and we need to have the
correct timezone entries in the SCCSv6 history files.
For the complete "schilytools" project with 4200 SCCS history
files in 55 Mbytes, this takes 12 seconds for the SCCS history
from 1984 .. 2020, but note that most of the edits from the
1980s are lost, so there are few entries from the time
before 1989.
An alternate example: the SCCS history from the BSD-4.4 project
from December 1979 up to June 1995 is in 12600 SCCS history
files that take up 125 MB.
The conversion time to the SCCSv6 history file format is
18 seconds.
- Call:
find * -path '*SCCS/s.*' | /opt/schily/ccs/bin/sccslog -changeset -
to populate the changeset file from the existing deltas.
For the complete "schilytools" project with 19600 commits,
this takes 8 minutes. The resulting file .sccs/SCCS/s.changeset
has a size of approx. 7 MBytes.
An alternate example: the SCCS history from the BSD-4.4 project
from December 1979 up to June 1995 has approx. 47000 commits.
The conversion time is approx. 40 minutes.
The size of the resulting changeset file is approx. 14 MBytes.
- convert the in-tree repository into an off-tree repository.
This final step is not yet needed and there is currently no
code to do that automatically.
- If you like to check the resulting changeset file, there is
currently only one way to look at it, by calling:
sccs -O get -p -A -m .sccs/SCCS/s.changeset | more
This prints an annotated version of the changeset file.
The next task is to develop an enhancement to "sccs log"
that prints the changeset in a way similar to what "hg log -v"
prints.
- NOTE: Normal filesystems on Linux are slow, it is advised to
make the conversions on tmpfs for performance reasons in case
you are using Linux.
Please however keep in mind that this is still experimental and there is
absolutely no grant that a changelog created with current experimental
software will work correctly with the final SCCS version. The procedure
is just an example to check how it may look like.
The final conversion method will be more automated... most likely
by a command similar to "sccs import ..."
IMPORTANT: This is not yet the time to finally convert a project into
the project mode, because the project would be stuck in the current
state. What we need to continue work in that repository state in the
project mode is at least a working "sccs commit". Be prepared to remove
the changeset history file once "sccs commit" works and to re-create
the changeset file for that time.
- SCCS TODO:
- Activate "fsdiff" as a "bdiff" replacement in delta(1)
to speed up delta(1) and to reduce the size of the SCCS
history files.
- Implement something that outputs similar information from
the changeset file as printed with "hg log -v".
This would be the next key feature.
- verify whether sccs.c uses -NSCCS in the back end programs
correctly, instead of converting g-file names from the command
line into s.file names in the frontend in order to forward
s.file names to the backend programs. This is needed for an
off-tree repository.
The related unit tests are already passed.
- Add code to to sccs(1) to send a list of files to admin(1) and
delta(1) with new or modified files in order to have all
important code for a "sccs commit" in a single program that
does not need to deal with ARG_MAX limitations.
- Add code to admin(1), delta(1), sccs-log(1) and get(1) to
maintain/understand the changeset file.
This is mainly writing out the sccschangeset(4) entries to an
intermediate store if a single file has been treated
successfully. For sccs-log(1), see below.
- Finish the work to allow normal line based diffs in SCCS even
for binary files. This are files that include nul bytes and
this needs to completely avoid fputs() and this needs an
initialized member p_line_length in struct packet even for
all content that does not result from a previous getline() call.
- sccs -R tell (and probably other subcommands?) does not yet
work in NewMode
- Add code to libcomobj to understand the changeset file.
This is needed in order to e.g. know the file names and file
specific SIDs/state that corresponds to a project global SID.
- Find/verify a complete transactional model that allows to repair
complex changes to the set of files for a project that have
been aborted in the middle. The current idea is to create the
file $PROJECTHOME/.sccs/changeset with the deltas to the
changeset during a complex update operation.
- Find a decision on how to deal with the admin flags that are
currently implemented as global flags and thus do not depend on
the SID (version) if the history file.
- Aborting a transaction via ^C currently requires a manual
removal of the global lock file. Find a way to avoid this in
case that a commit has been aborted while being prompted for
a commit message (which is before any real action happened).
- Implement a fully automated method to convert a SCCSv4 based
history with unrelated history files into a new SCCSv6 based
project mode history with a populated changeset history file.
This will most likely be done as a variant of the to be defined
new command "sccs sccsimport" that imports a whole existing old
SCCS project.
- Implement this "sccs sccsimport" based conversion in a way where
sccs(1) holds the global changeset lock for the whole time
of the conversion.
- Bourne Shell Missing features for POSIX compliance:
- Support for $'...' quoting (this is not needed for the current
version of POSIX but for the next POSIX
version that will be named SUSv8).
The development of SUSv8 will start in
late 2016.
We are now expecting the Bourne Shell to be fully POSIX compliant.
- Bourne Shell further TODO list:
- Finish loadable builtin support.
- POSIX does not allow us to implement ". -h", so we will
add a "source" builtin to be able to implement "source -h"
- The following builtins (that are available in bsh) are still missing in
the Bourne Shell:
err echo with output going to stderr
glob echo with '\0' instead of ' ' between args
env a builtin version of /usr/bin/env
The following bsh intrinsics are still missing in the Bourne Shell:
- the restricted bsh has restriction features that
are missing in the Bourne shell.
- source -h read file into history but do not execute
and probably more features not yet identified to be bsh unique.
Author:
Joerg Schilling
D-13353 Berlin
Germany
Email: [email protected]
Please mail bugs and suggestions to me.