Changes since 4.3.11
--------------------
The zsh/parameter module has a new readonly associative array
$usergroups whose keys are the names of system groups of which the
current user is a member and whose values are the corresponding
group identifiers.
The region_highlight array, which controls highlighting of the
command line from zle widgets, is now updated dynamically as
the command line is edited.
In POSIX emulation ("emulate sh") the shell is more accurate about
when it should or should not exit on errors.
The ${NAME:OFFSET:LENGTH} syntax now supports negative LENGTH, which
counts back from the end of the string.
The (g:opts:) flag in parameter expansion processes escape sequences like
the echo and print builtins. opts can be any combination of o, e and c.
With e, acts like print rather than echo except for octal escapes which
are controlled separately by the o option. With c, interpret control
sequences like "^X" as bindkey does. Regardless of the opts, \c is not
interpreted.
If a ports is linked against ncurses from base or from the ports, it should then add:
USE_NCURSES=yes
it is also possible to specify the hard dependency on the ports ncurses or one the base one adding the following macros:
WITH_NCURSES_PORT=yes or WITH_NCURSES_BASE=yes
PR: ports/155269
Submitted by: me
Reviwed by: pav@
Approved by: portmgr (pav@)
Exp-run by: portmgr (pav@)
* Make portlint happy by using ${ECHO}, and TABs in assignments.
PORTREVISION bump not required.
PR: ports/141728
Submitted by: olgeni
Approved by: des (by mail)
theory, but in practice, things will break if you set them to non-default
values. This allows us to unobfuscate the plist and fix a broken @dirrmtry.
Convert the NO_SHARED option to a proper port option (ZSH_STATIC).
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
Update csup, portsnap and portlint completion. Add completion for powerd,
freebsd-update, fetch and portaudit (from submitter) as well as zfs and
zpool (from zsh repo).
Bump PORTREVISION.
PR: ports/126457
Submitted by: baptiste.daroussin@gmail.com
script arrived at the correct value for ZSH_NO_XOPEN, but since autoheader
did not run, it did not propagate to config.h. Add autoheader to the
USE_AUTOTOOLS list to correct this.
