net-mgmt/icingaweb2-module-cube: drop maintainership

net-mgmt/icingaweb2-module-cube: drop maintainership

*/*: Unbreak with php84

These ports were initially marked to IGNORE with php84 as their runtime
dependencies were BROKEN. As all of the runtime dependencies has been
fixed for ther requirements unmark these ports. Although these ports
build perfectly with php84 but there might still be runtime issues with
these ports with php84. The maintainers are requested to do some runtime
checks for these ports.

Approved by:	portmgr (blanket)

*/*: Mark IGNORE_WITH_PHP=84

These ports are currently not compatible with php84 and is only a limited
set of ports. There might be more ports which has runtime issues. Please
check if your ports are compatible with php84 and if not pleae mark them
IGNORE_WITH_PHP=84

Approved by:	portmgr (blanket)

net-mgmt/icingaweb2-module-cube: Update to 1.3.2

Changelog: https://github.com/Icinga/icingaweb2-module-cube/releases/tag/v1.3.2

Sponsored by:	Netzkommune GmbH

net-mgmt/icingaweb2-module-cube: Update to 1.3.0

Sponsored by:	Netzkommune GmbH

net-mgmt/icingaweb2-module-cube: Update to 1.2.2

Sponsored by:	Netzkommune GmbH

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

net-mgmt/icinga*: - Take Maintainership

Sponsored by:	Netzkommune GmbH

*: Drop maintainership on most of my ports.

Unfortunately I cannot give them the love they deserve at the moment.

net-mgmt/icingaweb2-module-cube: Update to 1.1.1

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Fix dependency syntax

PR:		210021
Submitted by:	fluffy@
Reported by:	mat@

net-mgmt/icingaweb2 and modules:
- Drop stale dependency on www/zendframework1
- FLAVORize for all php releases
- Improve OPTIONS for supported databases

PR:		242664
Submitted by:	fluffy@

net-mgmt/icingaweb2-module-cube: Update to 1.1.0

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

net-mgmt/icingaweb2-module-cube:

- Update to 1.0.1

Add net-mgmt/icingaweb2-module-cube

The Cube is a tiny but useful Icinga Web 2 module. It currently shows host
statistics (total count, health) grouped by various custom variables in
multiple dimensions.

It will be your new best friend in case you are running a large environment and
want to get a quick answers to questions like:

- Which project uses how many servers per environment at which location/site?
- Who occupies most servers?
- How many of those are used in production?
- Which project has only development and test boxes?
- Which operating system is used for which project and in which environment?
- Do we still have Debian Lenny?