The logic in m4/strtoimax.m4 is inverted: it replaces strtoimax() if and only
if it is present and functional.
files/patch-configure avoids having to run autoreconf in the port and can be
removed once the fix has been adopted upstream.
differential Revision: https://reviews.freebsd.org/D36849
- point MASTER_SITES to new upstream
- split bosh from sysutils/schilyutils into new port shells/bosh
- stop installing pfbosh, a SunOS-only feature
- install jsh as jbosh to avoid a conflict
- patch shell names in man pages
- point WWW to subproject-specific sites if available
- misc/schilytools: deprecate man2html component
- devel/schilybase: add missing file to pkg-plist
- make test suite work better
- do not pass INS_*BASE/DESTDIR to smake tests
- account for devel/sccs placing files in /tmp
- make sh/tests/common/test-common find bosh after
we patched out the hardlink to sh
- Test suite passes on armv7 except for archivers/star.
Will have to investigate further.
- sysutils/schilyutils: add vctags command
I forgot about that one when I made the port initially.
The ctags link is not installed to avoid conflicts.
Changelog: http://fuz.su/pub/schilytools/AN-2022-09-18.txt
PR: 266475
ksh93 modernization development, which was halted in 2020, resulted in
the att/ast team saving the development in their ksh2020 branch and
reverting the mainline back to ksh93. Since the the ksh2020 developers
have forked ksh93 and resumed ksh2020 development under the ksh93
account in their ksh repository. Therefore the now "abandonware" ksh2020
ports is to be removed in favour of the shells/ksh or shells/ksh-devel
ports.
The shells/ksh port tracks releases while shells/ksh-devel tracks
development. shells/ksh93 is available for legacy applications that
require the original AT&T KSH93. The "co-existence" options of each
of these ports allow users to install shells/ksh (and/or ksh-devel) with
shells/ksh93 for users who wish to use the currently developed ksh93 but
still need the legacy AT&T ksh93 due to incompatibilties between the old
and the new. (Note: The latest CDE-25 develpment has switched to using the
new ksh93 shell.)
Commit b7f05445c0 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)
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)
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.
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.
Revert back the revert of the update of rust and related commits
This revert was drive by beside validation by portmgr via exp-run
and not respectful of the etiquette we have between committers
This reverts commit 8ecb1f8141.
This reverts commit 04d257baa1.
This reverts commit 2757c63bd0.
This reverts commit 75f4713de5.
This reverts commit e88e592111.
This reverts commit 783c056d7d.
With hat: portmgr
We used to modify the configure script to avoid zsh to link against
librt because clock_gettime on FreeBSD is in libc not librt.
It's been a while that we are configuring zsh with the --as-needed
linker flag which means now even if -lrt is passed we will not end
up linked to it librt anymore.
besides, modifying the configure script at the patch phase makes it
newer than stamp.h.in which results in the build system triggering a
regeneration of itself (hence the USES= autoreconf we had), not
touching anymore that script can remove the need for USES=autoreconf
and the load if build dependencies it drags in
Removing the USES=autoreconf highlights also the lack of build
dependency on perl which is needed to be able to the help files for
run-help to work on builtins. this is fixed now
Minor modifications to submitter's patch:
- Bump PORTREVISION since new tarball differs from the old one despite
both indicate the same version 1.7.4.
PR: 263631
Approved by: maintainer timeout
files/extra-patch-Src_Modules_curses__keys.awk is no longer needed
and broke patch phase if ports ncurses is installed.
The patch is already incorporated upstream, so doesn't apply.
