Log message:
shells/pbosh: Update to 20230112

New features with AN-2023-01-12:

UPDATING:

- Solaris 11.4: man pages are now installed according to BSD
 conventions. Users may need to manually remove the following
 old man pages on update: streamarchive.4, makefiles.4,
 makerules.4, changeset.4, sccschangeset.4, sccsfile.4,
 and star.4.

NEW FEATURES:

- libxtermcap/termcap: update to latest FreeBSD commit

- libxtermcap/termcap.url: remove file containing outdated
 information about where to obtain a termcap file from.

- RULES/os-sunos5.def: man pages will now be installed into
 BSD-style sections on Solaris >=11.4 and descendents.

- RULES: add symlink for arm64 OpenBSD

- Bourne Shell: Fix bug where set -o notify or set -b would cause
 the shell to exit when ^C was pressed.
 Submitted by Nico Sonack.

Log message:
shells/pbosh: Update to 20220918

Changelog from AN-2022-09-18:
With great sadness we report the death of schilytools main author and
long time maintainer Jörg Schilling (1955-03-27--2021-10-10). Jörg, we
miss you! After his passing, development has been picked up by a group
of volunteers who would like to keep the project alive and well. Our
goal is to carefully preserve the portability and compatibility of this
project while extending it to new platforms and implementing new tools
and features that fit the tool set.

As a part of the change in management, the schilytools project has moved
from Sourceforge to Codeberg.

- general: Explain how to contribute and update README

- general: Add list of contributors

- all: Misc spelling fixes
 Submitted by Friedhelm Mehnert.

- all: Update E-Mail address and project URL in many places.
 Jörg's old joerg@schily.net address is defunct and so is his
 postal address. As a part of an ongoing documentation cleanup,
 these addresses have been replaced by our new project pages in
 many locations.
 Submitted by Nico Sonack.

- man pages: work around buggy syntax highlighting by adding
 \" " comments into various places.
 Submitted by Nico Sonack.

- RULES: Fix build on macOS 12.4

- RULES: add i386-openbsd-clang.rul
 This should permit compilation on modern OpenBSD using clang as
 the system compiler.

- autoconf: Work around clang bug in #pragma weak detection.
 A clang compiler bug causing a crash in the configure test for
 #pragma weak has been worked around, permitting use of weak
 symbols when compiling with clang.

- tests: fix arm64/aarch64 architecture confusion on OpenBSD
 Submitted by Nico Sonack.

Log message:
shells/pbosh: Update to 20210918

Rebase to the final Schily Tools release.
The author Jörg Schilling passed away in October 2021.

Log message:
shells: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Log message:
shells: Remove SHA1 hashes for distfiles

Log message:
shells/pbosh: Update to 20210729

Changelog from AN-2021-07-29:
- Bourne Shell: "cd -" now prints the new directory. POSIX requires this.

 Thanks to a report from Robert Elz.

- Bourne Shell: "make install" now works wit SuPro Make as well.
 Previously, the target /opt/schily/xpg4/bin/bosh (a symlink) was not
 installed because of a missing rule that caused SuPro Make to complain.
 about a target with no existing rule to make.

- Bourne Shell: z/OS only supports the minimum fields from struct rusage
 that are required by POSIX. We need the same hack as for HAIKU to
 be able to compile.

 Thanks to a report from Matthew R. Wilson

- Bourne Shell: z/OS does not #define MAXPATHLEN, so we #define it
 to be 1024 by default

 Thanks to a report from Matthew R. Wilson

Log message:
shells/pbosh: Update to 20210607

Changelog from AN-2021-05-19:
- Bourne Shell: the fc(1) builtin now handles "fc -l -0" the same
 way as ksh does and refers to the current command. Before only
 "fc -l -1" did work to select the previous command.

 Together with the "ERR" trap fix, this permits to install a
 "command not found" handler in the shell that could explain users
 how to install a missing command.

 This "missing command" handler could be implemented via:

 trap 'show-info-message-for-missing-command $(fc -l -0)' ERR

Changelog from AN-2021-06-07:
- Bourne Shell: the man page now uses a correct notation for "[]" for
 the arguments of the builtin "dosh" that has been introduced in May
 2012.

Log message:
shells/pbosh: Update to 20210421

Changelog from AN-2021-01-05:
- Bourne Shell: When we introduced ${.sh.path} in February 2020, we did
 use the "new" and POSIX-only function realpath() that is not present
 on e.g. Ultrix. We now use abspath() from libschily if realpath() is
 missing.

 Note that abspath() is better than realpath(), as it supports path
 names longer than PATH_MAX, but since ${.sh.path} is only used to
 return the absolute pathname for the current shell binary, this is
 not a problem and on the other side, we can avoid linking against
 libschily this way, so shell scripting with lazy linking is faster
 since less libraries need to be linked at startup.

Changelog from AN-2021-04-21:
- 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