hikari: update to 2.3.0.

srcpkgs/hikari/INSTALL.msg

@@ -1,6 +0,0 @@
-Setting the SUID bit after install has been retired for all Wayland
-compositors. It is recommended that users use a session management daemon
-such as elogind or seatd and do not rely on compositors dropping privileges.
-
-All users who require this functionality will need to set the SUID bit manually
-after each update going forward.

srcpkgs/hikari/template

@@ -1,6 +1,6 @@
 # Template file for 'hikari'
 pkgname=hikari
-version=2.2.3
+version=2.3.0
 revision=1
 build_style=gnu-makefile
 make_cmd=bmake
@@ -16,8 +16,11 @@ license="BSD-2-Clause"
 homepage="https://hikari.acmelabs.space"
 changelog="https://hub.darcs.net/raichoo/hikari/browse/CHANGELOG.md"
 distfiles="${homepage}/releases/${pkgname}-${version}.tar.gz"
-checksum=0727d8652e6debea52a9d975bd656cb573556e0e14184b069925c40f2f1b02b4
+checksum=8577ea568d2a41b0dc7b2fae784446778e3ddd5b9563576c9756dfbf7b9435d2
 conf_files="/etc/pam.d/hikari-unlocker /etc/hikari/hikari.conf"
+# bmake's -q flag seems to differ in behavior from gnu make which causes the
+# build style's handling of the check target not existing to fail.
+make_check=no
 
 pre_build() {
 	# The hikari Makefile appends to the CFLAGS and LDFLAGS variables;
@@ -25,7 +28,7 @@ pre_build() {
 	# command line (i.e., when make_use_env is undefined), but it ignores
 	# the values in the environment when make_use_env=yes. The _EXTRA
 	# variables provided in the Makefile allow us to force the right flags.
-	export CFLAGS_EXTRA="${CFLAGS}"
+	export CFLAGS_EXTRA="${CFLAGS} -Wno-error"
 	export LDFLAGS_EXTRA="${LDFLAGS}"
 
 	# bmake tends to ignore CC in the environment