/www/mhonarc/

= construct. This hack was the only way I could figure out to make the flags properly conditionalize. Most commonly used build systems support silent builds, when they 2016-09-09T19:42:46+00:00 amdmi3 amdmi3@FreeBSD.org 2016-09-09T19:42:46+00:00 6e502d51f3f34690037f4f33bb5cf0f0f50e2ca7 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
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
Cleanup patches, a* categories. 2016-07-26T16:51:15+00:00 mat mat@FreeBSD.org 2016-07-26T16:51:15+00:00 92a23247b1467190ce10007190052c33423ff547 Rename them to follow the make makepatch naming, and regenerate them. With hat: portmgr Sponsored by: Absolight
Rename them to follow the make makepatch naming, and regenerate them.

With hat:	portmgr
Sponsored by:	Absolight
Remove ${PORTSDIR}/ from dependencies, Mk and categories a, b, and c. 2016-04-01T13:29:15+00:00 mat mat@FreeBSD.org 2016-04-01T13:29:15+00:00 96cd8e4bc2d30db4bc3bbbf3fcdcc98121c879e0 With hat: portmgr Sponsored by: Absolight
With hat:	portmgr
Sponsored by:	Absolight
Update MASTER_SITES; still in the same domain. 2016-02-09T21:46:55+00:00 gerald gerald@FreeBSD.org 2016-02-09T21:46:55+00:00 7311920027097b428e8e86af86d91e4816e2d8e6

audio/beast is not jobs safe 2016-01-15T06:51:04+00:00 marino marino@FreeBSD.org 2016-01-15T06:51:04+00:00 6b34fc13217fbb2a9448582abce1af4709a15fda It tries to use gxkmarshal.h before it's completely generated
It tries to use gxkmarshal.h before it's completely generated
mark some of the ports that don't build on powerpc64 for me 2015-12-13T16:07:27+00:00 swills swills@FreeBSD.org 2015-12-13T16:07:27+00:00 ca2098a7784c981483fe2afe0685e9dfdfa4079e

- Convert to option helpers, provide better support and defaults for SSE 2015-09-03T08:59:17+00:00 danfe danfe@FreeBSD.org 2015-09-03T08:59:17+00:00 9811e2707ba2db55903ec0c2f502e215b02deae7 - Remove BROKEN on powerpc statement which is no longer true these days - Wrap overly long USES line and move OPTIONS block lower while I'm here
- Remove BROKEN on powerpc statement which is no longer true these days
- Wrap overly long USES line and move OPTIONS block lower while I'm here
Part 1 of adding USE_GNOME=intltool to ports that require it. 2015-08-02T20:23:55+00:00 kwm kwm@FreeBSD.org 2015-08-02T20:23:55+00:00 8e06482685b64ce8d458dbb06943d4e18ee837cd The reason for this is that in the GNOME 3.16 update, USE_GNOME gtk20 and gtk30 don't pull intltool in anymore. PR: 201980 Exp-run by: antoine@
The reason for this is that in the GNOME 3.16 update, USE_GNOME gtk20 and
gtk30 don't pull intltool in anymore.

PR:		201980
Exp-run by:	antoine@