shells/ksh9393.u_4,2

shells/ksh93: mark as PIE_UNSAFE

PR:		286437
Approved by:	cy (maintainer)
Sponsored by:	Netflix

MAN?PREFIX: eleminate its usage  and move man to share/man

shells/ksh93: Remove blank line

Approved by:	portmgr (blanket)

shells/ksh*: Update descriptions

Update ksh ports descriptions to more accurately reflect what they are.

Reported by:	 "Joseph Holsten" <joseph@josephholsten.com>

shells/ksh: Remove the now expired ksh2020 from CONFLICTS.

shells/ksh93: Fix build with LLVM15

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.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

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)

*: fix tab vs. space issues, and comments according to the guide.

One more small cleanup, forgotten yesterday. Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Mark as BROKEN on riscv64 the same way as on aarch64.

Approved by:	portmgr (tier-2 blanket)

Fix i386 build.

AT&T AST (att/ast) on github has rewound their repo back to ksh93u+. See https://github.com/att/ast/issues/1464 and https://github.com/att/ast/issues/1466.

The reason for the rewind back to 93u+ instead of 93v- was that it was an
abandoned unstable buggy unfinished beta. A full explanation of this can be
found here, https://github.com/att/ast/issues/1466#issuecomment-589942449.

The version number is reverted back to 93u and an EPOCH bump, though not
needed, documents this siesmic shift.

Update MAINTAINER: use @FreeBSD.org

Add patch missed from r525497.

Fix CVE-2019-14868: certain environment variables interpreted as arithmetic expressions on startup, leading to code injection.

Submitted by:	Siteshwar Vashisht <svashisht@redhat.com>
Reported by:	Marian Rehak
MFH:		2020Q1
Security:	CVE-2019-14868
		https://bugzilla.redhat.com/show_bug.cgi?id=1757324
		https://access.redhat.com/security/cve/CVE-2019-14868

Update 2020.0.0 --> 2020.0.1

Update ksh-2020.0.0-beta1 --> ksh-2020.0.0.

Update 2020.0.0-alpha1 --> 2020.0.0-beta1

2020.0.0-beta1 resolves gcc9 build issues in PR/239644.

PR:		239644

Remove redundant GH_TAGNAME assignment.

shells/ksh93: Attempt to fix r508705 and unbreak index

It fails basic sanity checks:

make: "/usr/ports/shells/ksh93/Makefile" line 16: Malformed conditional (${USE_GCC} == "9")
make: Fatal errors encountered -- cannot continue
make: stopped in /usr/ports/shells/ksh93

PR:		239644
Pointy hat:	cy

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 

PR:		239644
Reported by:	pkubaj@

Whitespace adjustment.

Fix:

$ ksh93
$ time
../src/cmd/ksh93/sh/xec.c:2171: failed assertion 'tb.tv_sec'
Abort trap (core dumped)
$ ksh93
$ times
../src/cmd/ksh93/sh/xec.c:2171: failed assertion 'tb.tv_sec'
Abort trap (core dumped)

PR:		239701
Suggested by:	w.schwarzenfeld@utanet.at
MFH:		2019Q3

Fix build with GCC-based architectures.

PR:		239644
Submitted by:	pkubaj@
MFH:		2019Q3

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

devel/meson: Update to 0.51.0

Changes:	https://mesonbuild.com/Release-notes-for-0-51-0.html
PR:		238726
Submitted by:	greg@unrelenting.technology (update to 0.50.1)
Exp-run by:	antoine

shells/ksh93*: Do not set KSH93_DESC twice

Add missing wildcard to ksh93-devel conflict.

Register conflicts with the new shells/ast-ksh port.

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

shells/ksh93: Update to 93v 2014-12-24

PR:		208098 (fixed)
Submitted by:	saper@saper.info (maintainer)
Reported by:	fuz@fuz.su
Reviewed by:	cy@, pkubaj@
Approved by:	maintainer (implicit, submitter)
Differential Revision:	https://reviews.freebsd.org/D19343

Pet portlint.

Submitted by:	linimon@
Reported by:	linimon@
Approved by:	maintainer: Marcin Cieslak <saper@saper.info>

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

Register a conflict with the new ksh93-devel port.

shells/ksh93: Update reason for aarch64 broken message

Approved by:	bapt (mentor)
Differential Revision:	https://reviews.freebsd.org/D17204

- Always accompany OSVERSION check with OPSYS check

Approved by:	portmgr blanket

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)

- Pass maintainership to submitter

PR:		211164
Submitted by:	Marcin Cieslak <saper@saper.info>

Mark as broken on various tier-2 archs.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)

- Fix build on armv6 - While I'm here, fix diff header of patch file

PR:		209457
Submitted by:	<mikael.urankar@gmail.com>
Obtained from:	https://github.com/att/ast/blob/beta/src/lib/libast/hash/hashalloc.c
		https://github.com/att/ast/blob/beta/src/lib/libast/string/tokscan.c

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

- Fix build on 11-CURRENT

- Add my LOCAL to MASTER_SITES as backup - Use do-test: