- Also update dovecot auth patch to apply to this new version
- Properly convert to options and use options helpers
- Convert to new LIB_DEPENDS format
- Support staging
- Bump PORTREVISION
- While here perform a whitespace fix and move MAN* variables where
they belong.
Reported by: Bjoern Voigt <bjoernv@arcor.de> [1]
Feature safe: yes
logs. Default it to 72 (like in the sources), which plus the message size gives
80 (= standard # of columns in a terminal). If you watch the logs under X
something like 140 will probably use your screen width more usfully.
Approved by: maintainer
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)
- "WANT_FAM_SYSTEM=fam" might have been too restrictive,
so remove it.
Submitted by: KIMURA Yasuhiro <yasu utahime org>
PR: ports/112201
Approved by: maintainer timeout
was supposed to work is useless, because if we can't trust the distfile from
the remote machine, we can't trust the signature from the same machine either.
Our MD5 and SHA256 are good for checking both the sanity and the
trustiness of distfiles.
Approved by: portmgr (erwin), erwin (mentor)
- Install quotawarnmsg.sample file [1]
- Add WITH_FAM knob to explicitly enable optional support for FAM
in addition to autodetecting its presence; utilize USE_FAM for dependency
(choose between devel/gamin and devel/fam according to user's preference)
PR: ports/95169 [1]
Submitted by: Rui Lopes <rgl@ruilopes.com> [1]
"flock() failed" error when an attempting to route messages to /dev/null.
Patch is submitted upstream.
- Bump PORTREVISION
PR: ports/80106
Submitted by: David Lay <dsl@webize.com.au>
even if MAILDROP_SUID/MAILDROP_SGID option is set - fixed
NOTE: this changes behavior of these options so that suid/sgid bit
is set only if these options are explicitly specified.
There is no default value for these options now.
- Bump PORTREVISION
PR: ports/78715
Submitted by: KIMURA Yasuhiro <yasu@utahime.org>
(adds -rpath=${LOCALBASE}/lib/courier-authlib). Unlike the previous
solution (add it to LDFLAGS) this does work
PR: ports/77874
Submitted by: Thomas T. Velhdouse <veldy@veldy.net> (error report)
Obtained from: Douglas Fraser <doug@idmf.net> [1] (actual fix)
