New features with AN-2021-04-21: 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 psmake/smake install The new smake version mentioned above is smake-1.2.4 The recent smake version is smake-1.3 *** 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 as 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. 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 gmake fail in parallel mode. If you are interested in reliable parallel execution, it is recommended to use the included "dmake" program with a command line like: dmake -j10 -f SMakefile from the top level directory. Note that if you are on Linux, you need a halfway recent kernel or the compile time will not go down because of the low POSIX semaphore performance in older Linux kernels. 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. NEW FEATURES: - Schily.Copyright changed the Copyright for bosh/hdump/termcap to 2021 - Support for the platform earmv7-unknown-netbsd9.99.80 has been added to autoconf/config.guess and autoconf/config.sub as well to the script RULES/MKLINKS. Thanks to Eivind Nicolay Evensen for reporting - makefiles.tar.bz2 was updated to match the current state of the makefile system. - ./.links file now contains the new symlinks caused by the makefile system enhancements. - hdump/od: We now switch the operating mode for getargs(), - the option parser - to permit combined single char flags with the last flag having an argument in the combined string. This is required by POSIX option parsing but for good reasons not the default behavior for the getargs() option parser. Thanks to Stephane Chazelas for reporting the od(1) option -vto1 that did not work. - Bourne Shell: gmatch.c: The new version no longer aborts with an illegal multi byte sequence as "no match". As a result, the "*" now again matches any filename - even if the filename contains an illegal multi-byte sequence. This is a problem that did not exist on the original Bourne Shell from Solaris that used gmatch() from the AT&T libgen, but since we added our private portable gmatch.c to get better portability. Thanks to Stephane Chazelas for reporting the problem related to multi-byte to wide character conversion and illegal multi byte sequences in the case statement and filesystem globbing. - Bourne Shell: word.c::readwc() no longer uses prwc() but rather a loop on the original multi-byte stream to print the "set -v" output. This permits to output the original input data in any case instead of stumbling over illegal multi-byte sequences. Thanks to Stephane Chazelas for reporting the general problem with input byte sequences that cause an EILSEQ error. - Bourne Shell: struct fileblk now remembers lastwc and the related input string as fileblk->mbs[] in order to avoid incorrect conversions via wctomb() in case that the input wide char was a result from an EILSEQ conversion and thus has no related multi byte string. An important visible result of that change is that input read by the builtin command read(1) correctly forwards input that caused an EILSEQ error. It could not be verified whether this covers all possible similar cases, but it is at least very close to a completely correct solution. Thanks to Stephane Chazelas for reporting the general problem with input byte sequences that cause an EILSEQ error. - Bourne Shell: xec.c: Cstyle changes - Bourne Shell: the Copyright messages now mention 2021 - smake: We now support the idiosyncratic way, GNU make implements ::= that results in unpredictable behavior with larger makefiles since ::= creates a different macro type that causes the += operator to behave different from the usual way introduced in January 1986 by SunPro Make. += does not expand the right hand side before appending to an existing make macro since it has been introduced in January 1986. += now expands the right hand side before appending to an existing ::= typed macro. Such a macro is created if the first assignment to that macro is done via ::=. Using such a make macro does not expand such macros at use time. This includes expansions to the left side and the right side of a colon (:) dependency list and expansions for rule commands. - smake: The new operators :::= and +:= have been introduced in order to add an orthogonal (and thus better) counterpart to the GNU make ::= feature that has become part of the upcoming POSIX ISSUE 8. We will propose this as a new POSIX feature soon. In special since it has been implemented in smake and SunPro Make, see below. :::= assigns a normal make macro after expanding the right hand side +:= appends to any maro type after expanding the right hand side This permits predictable behavior for larger or structured makefile systems (based on the "include" statement), where it is not possible to know easily whether a mace macro has been created with a NAME=value assignment or with a NAME:=value assignment. Note that the official method in make since 45 years (since make exists) to prohibit macro expansion is not to use a ::= type macro but rather to use two '$' signs in the related value of the macro. - smake: The man page now mentions the new features - smake: The option -j maxjobs is now supported, but ignored. This makes smake compatible to the upcoming POSIX ISSUE 8 - smake: added a new function ungetch(). - smake: version bumped to 1.4 - SunPro Make: The new operators :::= and +:= have been introduced in order to add an orthogonal (and thus better) counterpart to the GNU make ::= feature, identically to the new smake feature. - SunPro Make: We now support the idiosyncratic way, GNU make implements ::= that results in unpredictable behavior since ::= creates a different macro type that causes the += operator to behave different from the usual way introduced in January 1986 by SunPro Make. += now expands the right hand side before appending to an existing ::= typed macro. Such a macro is created if the first assignment to that macro is done via ::=. - SunPro Make: The man page now tries to avoid a page break in the middle of a short paragraph. - SunPro Make: TODO: Add support to handle make macros created via ::= to not expand at use time. This includes expansions to the left side and the right side of a colon (:) dependency list and expansions for rule commands. Note that the effort to implement that GNU make feature is currently unknown but is expected to be significant. - termcap: A new option -e has been added to tell termcap(1) not to ignore the TERMCAP environment in case that it contains a pre parsed termcap entry. This helps to analyze the current termcap entry in case that it is a "managed" pre parsed entry in the current TERMCAP environment. This is the case when called from within the screen(1) command or with modern shells (where this feature was introduced in 1985). 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 - 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: joerg@schily.net Please mail bugs and suggestions to me.