shells/bosh: 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

2 files changed, 8 insertions, 8 deletions

diff --git a/shells/bosh/Makefile b/shells/bosh/Makefile
index ad204363d68..cd7d82681d6 100644
--- a/shells/bosh/Makefile
+++ b/shells/bosh/Makefile
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.17 2020/11/25 15:52:06 micha Exp $
+# $NetBSD: Makefile,v 1.18 2021/04/26 10:45:39 micha Exp $
 
-DISTNAME=	schily-2020-11-25
-PKGNAME=	bosh-20201125
+DISTNAME=	schily-2021-04-21
+PKGNAME=	bosh-20210421
 CATEGORIES=	shells
 MASTER_SITES=	${MASTER_SITE_SOURCEFORGE:=schilytools/}
 EXTRACT_SUFX=	.tar.bz2
diff --git a/shells/bosh/distinfo b/shells/bosh/distinfo
index b7808c929c5..fd42c564556 100644
--- a/shells/bosh/distinfo
+++ b/shells/bosh/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.14 2020/11/25 15:52:06 micha Exp $
+$NetBSD: distinfo,v 1.15 2021/04/26 10:45:39 micha Exp $
 
-SHA1 (schily-2020-11-25.tar.bz2) = 9ca25eb2a0c3d583e5ca6ef11d1670f8a79914d5
-RMD160 (schily-2020-11-25.tar.bz2) = 61d0aa46cc485e220ae46b95a1d318e899a8638c
-SHA512 (schily-2020-11-25.tar.bz2) = 6592e34eb53ef83b1b15e91ac65e5dace88ee62dba3d4b24b7e4b01b052e235b682ab87af266bceeab8a0be796e6105328975e88b12e37c541797ee9786bb01e
-Size (schily-2020-11-25.tar.bz2) = 4899985 bytes
+SHA1 (schily-2021-04-21.tar.bz2) = 81f87aba8f31caa9decbbe605aa40c9b631474c9
+RMD160 (schily-2021-04-21.tar.bz2) = 0f35a4a9e4e464d7bbf40758c0d6fa314f7e4381
+SHA512 (schily-2021-04-21.tar.bz2) = feb6150fbf79b9a12be58325eac328393c504635f461993b24edcfc18df53953b4c28390187c38c8eccc8cc905354b8fb2f50f5f60beb04363bb9ce32d8203e6
+Size (schily-2021-04-21.tar.bz2) = 4919718 bytes