As before, there are attempts to use object files before they are
fully built. It's failed on me twice since the previous MAKE_JOBS_UNSAFE
marking was removed. An explicit fix should be made to the vendor
makefile before removing it again.
PR: 210545
Submitted by: Dave Cottlehuber <dch@skunkwerks.at>
Riemann-C-client is a C client library for the Riemann monitoring system,
providing a convenient and simple API, high test coverage and a copyleft
license, along with API and ABI stability.
https://github.com/algernon/riemann-c-client/#readme
USES=localbase:ldflags can be used to set LDFLAGS. Normally LDFLAGS
appears too early on the command line causing some ports to link with
their own libraries in LOCALBASE (if installed) instead of WRKSRC.
Also make use of _USES_POST so -L${LOCALBASE}/lib is added as late as
possible after anything a port Makefile might set. Use _USES_POST
instead of .include in libedit.mk and libarchive.mk so things like
'USES=libedit localbase:ldflags' work correctly.
Fix some issues with LIBS in some ports.
Switch ports that don't support LIBS to localbase:ldflags.
PR: 212987
Exp-run by: antoine
Approved by: portmgr (antoine)
The file lib/collectd/disk.so was being commented out in pkg-plist for
all FreeBSD versions instead of just for versions less than 10.
Reported by: pierre@guinoiseau.eu (via ports-committers@)
Reviewed by: swills (mentor)
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D8042
- new port options CHRONY and MQTT
- disable disk plugin on FreeBSD 9.x due to missing OS files
- various patch changes
PR: 212832
Submitted by: ports@bsdserwis.com (maintainer)
Reviewed by: swills (mentor)
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D8028
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
I think the original makefile was starting that the FreeBSD 9 base OpenSSL
isn't good enough. My previous commit lost that information, so put the
equivalent check back again.
Zabbix3-server can't be built by LibreSSL because it uses PSK. It also
can't be built by FreeBSD 9 base OpenSSL. The latter was documented, but
the solution in the notification was incorrect, so improve all that.
Approved by: SSL blanket
These ports currently utilize PSK which is not supported by LibreSSL, so
detect that SSL_DEFAULT and set IGNORE accordingly. The obsolete
USE_OPENSSL_PORT logic was also removed.
Approved by: SSL blanket
The py4suite option probably didn't work even before the py4suite
dependency was removed from the tree 2 years ago.
The MACRESOLV option fetches during the build which is illegal and
maybe is hitting a bad URL because it freezes as well.
The py4suite has been removed completed and the MACRESOL option has
been marked broken. This is after I rearranged the port to make them
even work as intended. I cleaned up the port a lot after documenting
the SSL requirement with USES=ssl.
Approved by: just-fit-it and SSL blankets
- The hardecoded 3des cipher for ssh has been removed upstream
- Remove a patch that automatically attempts to "svn up" before
checking in changes. This patch may have been committed accidentally a
couple years ago and deviates from upstream's behavior.
If it is possible for your rancid svn repository to be updated outside
of rancid's control it is up to you to resolve these potential
conflicts and modify your scheduled rancid process to "svn up"
beforehand. By instructing rancid to do this automatically it is
possible for an administrator to make device config changes that rancid
will not detect and will not show up in the automatic emails dispatched
to the device administrators.
hide actual commands executed and only show short summary line (like
"CC foo.c"). CMake and ninja enable this by default, some autotools
using ports do as well. This is unacceptable because we need complete
build logs at any time, so we now switch to verbose build logs
unconditionally. Note that this change deliberately affects ALL
builds and not only package builds on cluster, because we need to
be sure that user experiencing failure can always provide informative
build log regardless of settings and without rerunning the build.
Change summary:
- Always do verbose builds for cmake, ninja and GNU configure (the
latter includes check if --disable-silent-rules is actually supported
by the configure script; there are isolated cases when it's not true)
- Remove CMAKE_VERBOSE, NINJA_VERBOSE and
CONFIGURE_ARGS=--disable-silent-rules from all ports which set them
for this is no longer needed
- Revert hacks for --disable-silent-rules support priorly committed
to biology/ncbi-blast+ and net-p2p/mldonkey - no longer needed as well
Submitted by: amdmi3
Reviewed by: mat
Exp-run by: antoine
Approved by: portmgr (mat, antoine)
Differential Revision: D7534
