ksh93u+ is the 2012-08-01 (stable) 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. ksh93u+ provides an enhanced
programming environment in addition to the major command-entry
features of the BSD shell "csh". With ksh93u+, medium-sized programming
tasks can be performed at shell-level without a significant loss
in performance. In addition, "sh" scripts can be run on ksh93u+
without modification.
===> The following configuration options are available for ksh93-93.u_4,2:
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
KSH93L=off: Install to /usr/local/bin/ksh93l (legacy)
===> Use 'make config' to modify these settings
shells/ksh*: Update descriptions
Update ksh ports descriptions to more accurately reflect what they are.
Reported by: "Joseph Holsten" <joseph@josephholsten.com>
devel/ksh93: remove sbrk() use
ksh supports multiple sources of heap memory. Completely disable the
use of sbrk() as a memory source in favor of mmap(). This allows
compilation on aarch64 (and presumably riscv64).
Approved by: cy
Differential Revision: https://reviews.freebsd.org/D37312
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
shells/ksh*: Allow the ksh ports to coexist
Add an option to allow the ksh ports to avoid conflicting with each
other and to coexist. This allows people who wish to punish themselves
by tracking developent to still be able to fall back should upstream
cause regressions.
This also allows legacy ksh93 to coexist with the recently added
ksh93/ksh, which is not entirely compatible with legacy ksh. Applications
which require a legacy ksh compatible package should use the ksh93 port
installed using one of its options. This allows new and old to exist on
the same system.
*/*: 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 broken when USE_GCC=9. Upstream git commit
63e9edcb6084d4b164439065e2d71f3e900ec3c7 resolves this issue.
Unfortunately it does not apply, requiring this port to be upated to
ksh93 well into ksh93-devel. Bringing ksh93 up to the ksh93-devel or
shy of it would negate the justification for ksh93's existence. It is
therefore recommended that people use ksh93-devel on architectures that
use GCC 9 or use GCC 8.
PR: 239644
Reported by: pkubaj@
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
Fix version going backward due to update to 2020.0.0.a1 (pointy hat to
yours truly).
The maintainer no longer wants to maintain ksh93 as his desire is to
maintain a backlevel port of ksh93 in order to build and support a
shared library for use by legacy applications, which is inconsistent
with the direction of the att/ast team on github. I will maintain the
port.
PR: 237332
PR: 238266
Approved by: maintiner (saper@saper.info)
This is the second part of a two part commit Updating shells/ksh93 to
2020.0.0-alpha1.
This commit:
1. Deletes shells/ksh93, completed by r502844.
2. svn copies shells/ksh93-devel to shells/ksh93 -- this commit.
3. Replaces the git tag with DISTVERSION 2020.0.0-alpha1 -- this commit.
PR: 237332
Reviewed by: crees@
Approved by: maintainer timeout
Reminded by: Siteshwar Vashisht <svashisht@redhat.com>
(ksh93 upstream maintainer)
This is the first part of a two part commit to update shells/ksh93 to
2020.0.0-alpha1.
Following this commit will be an svn copy shells/ksh93-devel to
shells/ksh93, replacing the git tag with DISTVERSION 2020.0.0-alpha1.
PR: 237332
Approved by: maintainer timeout
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
shells/ksh93: Fix build with gcc5
The ksh93 build process requires the pre-GCC5 CPP newline behavior, which
the -P argument provides by disabling line markers. This enables ksh93
to be built by gcc5 and later.
Approved by: GCC blanket
PR: 216707 (related)
Remove unnecessary evals that do-fetch was using.
Turns out that env(1) knows how to parse a properly quoted string
using -S "string", it makes the double eval used for the fetch
command to be unnecessary.
This is because running:
eval "foo $(escape $bar)"
is silly when this works:
foo $bar
So remove escaping and quoting, and sillyness.
PR: 210198
Submitted by: mat
Exp-run by: antoine
Sponsored by: The FreeBSD Foundation, Absolight
Differential Revision: https://reviews.freebsd.org/D6779
Add an @shell keyword to handle adding and remove a shell path in /etc/shell
Bump port revision of all ports that were doing it wrong prior to the keyword
CR: D208
Reviewed by: antoine
With hat: portmgr
- Update to 2008-11-04
- This version fixes the breakage on -current after the TTY changes.
PR: ports/128586
Submitted by: Joe Kelsey <joe@zircon.seattle.wa.us> (maintainer)
Update to 2007-03-28.
Keep BROKEN on sparc64 - it still doesn't compile.
PR: ports/111165
Submitted by: Joe Kelsey <joe -at- zircon.seattle.wa.us> (maintainer)
