meson: fix tristate behavior for systemd_notify option
The old logic was broken for the 'auto' case in that HAVE_SYSTEMD_DAEMON was only defined when systemd_notify was 'true'.
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
The old logic was broken for the 'auto' case in that HAVE_SYSTEMD_DAEMON was only defined when systemd_notify was 'true'.