KSH-93 is the most recent version of the KornShell Language described
in "The KornShell Command and Programming Language," by Morris
Bolsky and David Korn of AT&T Bell Laboratories. The KornShell is
a shell programming language, which is upward compatible with "sh"
(the Bourne Shell), and is intended to conform to the IEEE P1003.2/ISO
9945.2 Shell and Utilities standard. KSH-93 provides an enhanced
programming environment in addition to the major command-entry
features of the BSD shell "csh". With KSH-93, medium-sized programming
tasks can be performed at shell-level without a significant loss
in performance. In addition, "sh" scripts can be run on KSH-93
without modification.
WWW: http://www.kornshell.com/
===> The following configuration options are available for ksh93-devel-2020.06.30:
EXAMPLES=on: Build and/or install examples
STATIC=off: Build static executables and/or libraries
====> Options available for the single BIN_KSH: you have to select exactly one of them
KSH=off: Install to /usr/local/bin/ksh
KSH93=on: Install to /usr/local/bin/ksh93
===> Use 'make config' to modify these settings
shells/ksh93-devel: Rename to ksh-devel
ksh development has resumed under a new account on github. Renaming
shells ksh93-devel to ksh-devel is the fist step in tracking ksh93
development again.
*/*: Remove redundant '-*' from CONFLICTS definitions
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
Mark ports that are BROKEN due to sbrk on aarch64, also BROKEN on riscv64
where appropriate.
While here, pet portlint (Makevar order; whitespace).
Approved by: portmgr (tier-2 blanket)
Update to the latest att/ast github commit. Includes:
Merge pull request #1482 from lkoutsofios/master
change for gcc v10
change to ps.c to remote pid size check
change to sfputr.c to disable use of memccpy
change to cmdarg.c to adjust argument length calc. due to failures in tw
Resolve distfile mismatch from r526860.
The update sat in my git tree for a couple of weeks before merging the
branch. I updated the commit date without regenerating distfile.
Pointy hat to: cy
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Update to the latest att/ast github commit.
This includes fixes for a use after close and unchecked return value.
> Description of fields to fill in above: 76 columns --|
> PR: If and which Problem Report is related.
> Submitted by: If someone else sent in the change.
> Reported by: If someone else reported the issue.
> Reviewed by: If someone else reviewed your modification.
> Approved by: If you needed approval for this commit.
> Obtained from: If the change is from a third party.
> MFC after: N [day[s]|week[s]|month[s]]. Request a reminder
email.
> MFH: Ports tree branch name. Request approval for merge.
> Relnotes: Set to 'yes' for mention in release notes.
> Security: Vulnerability reference (one per line) or
description.
> Sponsored by: If the change was sponsored by an organization (each
collaborator).
> Differential Revision: https://reviews.freebsd.org/D### (*full* phabric URL
needed).
> Empty fields above will be automatically removed.
M ksh93-devel/Makefile
M ksh93-devel/distinfo
Update to the latest att/ast github commit.
`${foo.__}` should not expand to parent node
This was an experimental feature that was added after last stable
release. Disable it.
Fixes upstream issue #1116.
Update to the latest att/ast commit on github.
This brings in the following important commit on github:
Ensure fd 0, 1, 2 are never closed
Closing stdin, stdout, or stderr is extremely dangerous and
should never be done. If an attempt is made to do so redirect
the file descriptor to /dev/null. Similarly, if ksh is started
with one of those fd's closed open it on /dev/null before doing
anything else.
Resolving upstream issue #1117.
Update to the latest ast/ksh93 github commit.
Notable fixes:
Fix `${+}` parameter expansion inside loops
`nv_getval()` function internally calls `nv_optimize()` and
optimizations outside `varsub()` function depend on it. Using
`nv_isnull()` instead of `nv_getval()` was causing broken behavior
with `${+}` parameter expansions inside loops.
Resolves: #70
Update to the latest ast/ksh93 github commit.
Notable fixes are:
Sync all streams before restoring file descriptors
This was causing issues while truncating files. Sync all streams
before restoring file descriptors to avoid any similar issues in
future.
Remove compatibility code for FreeBSD < 11.2 from all ports.
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
Update to the latest ast/ksh93 github commit. From their commit log:
Coverity Out-of-bounds read
This Coverity Scan issue appears to be a false positive.
This change is a reformulation of the code that attempts
to both clarify the behavior and suppress the false positive
error.
Coverity CID#316729
Update to the latest ast/ksh93 github commit, specifically to bring
in from upstream:
Coverity Out-of-bounds access error
The call to `nv_addtype()` is passing the wrong structure length.
Coverity CID#279500
As ksh93 is the real ksh devleoped by AT&T, git the user the option
of installing ksh as ${LOCALBASE}/bin/ksh instead of as
${LOCALBASE}/bin/ksh93. If the KSH option is chosen, this port will
conflict with shells/pdksh. By default the binary that is installed is
ksh93 (conflicting with shells/ksh).
In the future, we might want to add a little ports infrastructure
allowing ports that need a ksh to depend on one of the various ksh or
ksh clones in ports.
2008-10-19 x11-wm/flwm: Project is dead, and uses obsolete version of fltk
2008-09-19 x11-wm/kahakai: "Development ceased"
2008-08-24 palm/synce-gnomevfs: No longer supported by developers
2008-08-24 palm/synce-kde: No longer supported by developers
2008-08-24 palm/synce-multisync: No longer supported by developers
2008-12-06 shells/ksh93-devel: This port is Outdated. Please use shells/ksh93
2008-09-19 sysutils/dtc-toaster: Has been broken for more than 6 months
2008-09-19 sysutils/dusage: Has been broken for more than 6 months
2008-09-19 games/linux-alienarena: Has been broken for more than 6 months
With the update to shells/ksh93 this port is now outdated. The
maintainer has stated he does not intend to keep it updated. Schedule
for removal in a month.
