- Takeover maintainership
- Merge changes from shells/bash-devel this updates the port to 4.3
- Remove the now useless -devel ports
- Document change in ports/MOVED
Approved by: portmgr (bapt)
Ensure the configure script always activate the same features wether or not
fdescfs is mounted: Always consider /dev/fd as absent
Bump portrevision as packages on the cluster are built with fdescfs mounted.
With hat: portmgr
Reported: Derek Schrock (skered- via #poudriere)
It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build
it brings bison as a run dependency in case it is set the following way:
USES= bison:run
it brings bison both as a run and build dependency in case it the set the following way:
USES= bison:both
While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix
* If a backslash-newline (which is removed) with no other input is given as
input to `read', the shell tries to dereference a null pointer and seg faults.
* Under certain circumstances, bash attempts to expand variables in
arithmetic expressions even when evaluation is being suppressed.
* Output redirection applied to builtin commands missed I/O errors if
they happened when the file descriptor was closed, rather than on write
(e.g., like with an out-of-space error on a remote NFS file system).
* Process substitution incorrectly inherited a flag that inhibited using
the (local) temporary environment for variable lookups if it was providing
the filename to a redirection. The intent the flag is to enforce the
POSIX command expansion ordering rules.
Under certain circumstances, running `fc -l' two times in succession
with a relative history offset at the end of the history will result
in an incorrect calculation of the last history entry and a seg fault
PR: 160239
Plain "bison -d parse.y" outputs parse.tab.c instead of y.tab.c,
so y.tab.c is never regenerated, and the parser fix from patch 001
is effectively not applied.
PR: 139720
Approved by: maintainer timeout (4+2 weeks)
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)
