---
- branch: MAIN
  date: Tue May 12 09:06:39 UTC 2020
  files:
  - new: '1.11'
    old: '1.10'
    path: pkgsrc/shells/pbosh/Makefile
    pathrev: pkgsrc/shells/pbosh/Makefile@1.11
    type: modified
  - new: '1.9'
    old: '1.8'
    path: pkgsrc/shells/pbosh/distinfo
    pathrev: pkgsrc/shells/pbosh/distinfo@1.9
    type: modified
  id: 20200512T090639Z.dc83fc55e3194a21e846fdfd7eb974f847296b5c
  log: "pbosh: Update to 2020-05-11\n\ntbl of NetBSD does not work, install man page
    with unprocessed tables as\nworkaround.\n\nChanges from AN-2020-03-11:\n-\tconfigure:
    The autoconfiguration now has an enhanced test for waitid()\n\tthat was needed
    since Mac OS is still not POSIX compliant and returns 0\n\tinstead of the signal
    number for a process that has been killed by a\n\tsignal. MacOS did pass the POSIX
    certification as a result of a missing\n\ttest for that problem.\n\n\tSince every
    vertified OS needs to run an annual refresh the\n\tcertification with recent versions
    of the test, I guess that\n\tMac OS (Catalina updates) may become more compliant
    witin a year.\n\n-\tpsmake: The portable bootstrap compile environment for smake
    missed\n\ta symlink for unsetenv.c to libschily since the related code has been\n\tmoved
    to libschily in 2018. This prevented compilation on IRIX.\n\n\tThanks to Kazuo
    Kuroi for reporting\n\n-\tlibshedit: mystdio.h now calls #undef sprintf and #undef
    snprintf\n\tbefore redefining the names. This avoids clang warnings on MacOS.\n\n-\tBourne
    Shell: set -m now works in scripts as well. Before, bosh did\n\tnever call startjobs()
    when the shell startup was done with a shell\n\tscript.\n\n-\tBourne Shell: The
    shell now supports the alternate ;& switch\n\tcommand limiter in addition to ;;
    where ;& implements a fallthrough\n\tto the next command list regardless on thether
    there is a match or not.\n\n-\tBourne Shell: The file xec.c has been reindented
    for the \"case\" support\n\tcode in the interpreter. The indentation is now one
    tab less so code\n\tbecomes more readable.\n\n-\tved/bsh/bosh: map.c now includes
    better command for the routines that\n\timplement fallback to some basic mapping
    when no user defined mapping\n\thas been set up.\n\nChanges from AN-2020-03-27:\n-\tBourne
    Shell: The case statement now supports the alternate end case\n\tsymbol \";;&\"
    that has been introduced by bash. If \";;&\" is used instead\n\tof \";;\", the
    next pattern list is evaluated and if there is a match,\n\tthe related command
    list is executed.\n\nChanges from AN-2020-04-18:\n-\tBourne Shell: IRIX has ls(1)
    installed as /sbin/ls and this caused\n\tsome of our unit tests to fail. We now
    only check for \"bin/ls\" and\n\tno longer for \"/bin/ls\" in \"type\" return
    messages.\n\n-\tBourne Shell/bsh: signames.c has been modified to work correctly
    if the\n\tnumber of statically defined realtime signals is odd. This applies to\n\tNetBSD
    and caused the shells to miss RTMIN+15 on NetBSD.\n\n\tThanks to Robert Elz for
    reporting\n\n-\tBourne Shell: A new trap code \"ERR\" as been introduced. This
    is modeled\n\tafter a feature from ksh88. \"trap cmd ERR\" causes \"cmd\" to be
    called\n\twhenever a command causes a non-zero exit code. The \"cmd\" is not called\n\tin
    case that with \"set -e\" the shell would not exit.\n\n\tThis is not required
    by POSIX but helpful.\n\n-\tBourne Shell: A new set of unit tests for the ERR
    trap has been added.\n\n-\tBourne Shell: An attempt to fix the POSIX behavior
    for set -e from\n\tOctober 2018 has been identified to be wrong. If we kept that
    change,\n\ta list with \"set -e; ...\" and a failing command would not exit as\n\texpected.\n\n-\tBourne
    Shell: A new piece of code has been added to handle set -e\n\tfor function calls.\n\n-\tBourne
    Shell: The man page now better explains the behavior, if in\n\tset -e mode.\n\n-\tBourne
    Shell: print.c::prs_cntl() could cause a buffer overflow with\n\t\"unprintable\"
    multi byte UNICODE characters that are printed as list\n\tof octal escape sequences.
    the buffer overflow happened because there\n\twas only redzone space for one such
    octal escape sequence.\n\n\tThanks to Heiko Ei�feldt for reporting\n\nChanges
    from AN-2020-05-11:\n-\tMakefile system: A new version of the BSD make (bmake)
    program fixed\n\ta bug in pattern macro substitution, so we are now able to detect\n\tBSD
    make and to read BSD make program specific rules.\n\n\tThis could in theory allow
    us to support BSD make in the future,\n\tbut...\n\n\tNote that we on the other
    side discovered a new bug with pattern\n\tmacro substitution in bsd make: The
    substitution:\n\n\t\t$(FOO:%=bar/%)\n\n\tis replaced by \"bar/\" with an empty
    \"FOO\", but of course, with an\n\tempty FOO, the substitution should be empty
    as well.\n\n\tThis second bug (above) was fixed on May 6th, but we do not yet
    have\n\tall needed make rules and we do not know whether other bugs may still\n\tprevent
    the usability of BSD make. Supporting BSD make will be hard\n\tas BSD make does
    not support pattern matching default rules and this\n\tis important for placing
    the .o files into a sub-directory.\n\n\tAlso note that the portable program source
    for \"bmake\" from \"pkgsrc\"\n\tis 2 years old and thus currently cannot be supported
    at all. If\n\tyou like to experiment on your own, you need to get this version:\n\n\t\thttp://crufty.net/help/sjg/bmake.html\n\n\tsee\n\n\t\thttp://www.crufty.net/ftp/pub/sjg/bmake.tar.gz\n\n\tand
    replace the newer files from the netbsd.org CVS tree by hand in\n\torder to fix
    the first and second mentioned pattern macro substitution\n\tbug.\n\n-\tMakefile
    system: RULES/MKLINKS was enhanced to create a new symlink\n\tRULES/r-bsdmake.tag
    that points to RULES/r-make.tag\n\n-\tMakefile system: The archive makefiles.tar.bz2
    has been added to the\n\tschilytools tree to allow easy reuse of the makefile
    system for own\n\tprojects.\n\n-\tBourne Shell: The unit tests for the new ERR
    trap did not work on\n\tSolaris because /bin/false on Solaris causes an exit code
    of 255.\n\tWe now only check for an exit code != 0.\n\n-\tBourne Shell: Some of
    the unit tests for the trap command are now only\n\trun in case that the SUT is
    \"bosh\".\n\n-\tBourne Shell: set -- now checks the '\\0' character at the end
    of\n\tthe string \"--\". This fixes strange behavior with argument strings that\n\tstart
    with \"--\".\n\n-\tBourne Shell: Added a new flag XEC_INFUNC to the xflag parameter
    to mark\n\tthe fact when inside a function.\n\n-\tBourne Shell: set -e no longer
    causes commands with nonzero exit code\n\tto abort inside a function in case that
    the return code of that function\n\tis evaluated by e.g. an \"if\" statement.\n\n\tThanks
    to Koichi Nakashima for reporting\n\n-\tBourne Shell: A unit test for the above
    bug has been added.\n\n-\tBourne Shell: $- may no longer be partially wrong (and
    miss the state\n\tof the -e flag).\n\n\tThanks to Koichi Nakashima for reporting\n\n-\tBourne
    Shell: under some rare conditions, the syntax tree -> cmdline\n\tconverter could
    omit a command delimiter. This was the result of the\n\tfact that a helper variable
    \"didnl\" (used for codeoutput beautifying)\n\twas not reset in func.c and thus
    could cause\n\n\t\tprintf a ; printf b\n\n\tto print \"aprintf b\" instead of
    \"ab\"\n\n\tThanks to Koichi Nakashima for reporting\n\n-\tBourne Shell: A unit
    test for the above bug has been added.\n\n-\tBourne Shell: A command like:\n\n\t\tcommand
    | while read name; do loopcmd; done\n\n\tdid stop after the first loop because
    \"read\" did then read from stdin\n\tinstead of using the pipe file descriptor.
    This happened only of\n\t\"loopcmd\" was not a shell builtin.\n\n\tThanks to Koichi
    Nakashima for reporting\n\n-\tBourne Shell: A unit test for the above bug has
    been added.\n\n-\tBourne Shell: When we added support for ${var+value with spaces}\n\t4
    years ago, we forgot to enhance the lexer the same way for things\n\tlike \"${var+value
    with spaces}\" and \"${var+\"value with spaces\"}\".\n\tThis has been forgotten,
    because a different part of the lexer is\n\tused to parse that kind of quoted
    strings. The lexer now supports\n\tlooking for closing '}' in quoted text as well.\n\n\tThanks
    to Koichi Nakashima for reporting\n\n-\tBourne Shell: A unit test for the above
    bug has been added.\n\n-\tBourne Shell: The expression \"${var1#\"$var2\"}\" has
    been introduced by\n\tksh88 with strange rules for the way the double quotes past
    # are\n\thandled. We now support them....\n\n\tThanks to Koichi Nakashima for
    reporting\n\n-\tBourne Shell: A unit test for the above bug has been added.\n\n-\tBourne
    Shell: Some unit tests from \"mksh\" (that previously have been\n\tdisabled) have
    been enabled, since the two changes above now make\n\tthe Bourne Shell behave
    like \"mksh\" for these 6 additional tests.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/shells/pbosh'
  unixtime: '1589274399'
  user: micha