head	1.2;
access;
symbols
	pkgsrc-2026Q1:1.1.0.6
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.4
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.2
	pkgsrc-2025Q3-base:1.1;
locks; strict;
comment	@# @;


1.2
date	2026.05.03.16.39.13;	author gdt;	state Exp;
branches;
next	1.1;
commitid	2kVTi6aNII9T8oEG;

1.1
date	2025.09.10.11.08.57;	author jperkin;	state Exp;
branches;
next	;
commitid	sx8mAyWtAUwSR9aG;


desc
@@


1.2
log
@sysutils/ups-nut: Update to 2.8.5

Release notes for NUT 2.8.5 - what's new since 2.8.4
----------------------------------------------------

 - common code:
   * Introduced `NUT_DEBUG_PROCNAME` environment variable support to optionally
     log also the process name (or however the program chose to identify itself).
     This may be useful when multiple NUT daemons log into the same file or
     console, without syslog to prefix the name into each line (e.g. in tests,
     single init script systems like Home Assistant, etc.) [PR 3368]

 - `asem`, `bestfortress`, `bestuferrups`, `bicker_ser`, `everups`, `metasys`,
   `masterguard`, `mge-utalk`, `oneac`, `phoenixcontact_modbus`, `pijuice`,
   `powercom`, `powervar_cx_ser`, `usbhid-ups`, `victronups` driver updates:
   * Moved code to align with NUT driver architecture, so `upsdrv_initups()`
     would focus on preparing communications, and `upsdrv_initinfo()` would
     actually talk to the device and set initial critical data values. [#1962]

 - Introduced a new NUT driver named `meanwell_ntu` which provides support for
   the Mean Well NTU series hybrid inverter and UPS units. [PR #3206]

 - Introduced a new NUT driver named `must_ep2000pro` which provides support
   for the MUST EP2000Pro compatible, line-interactive UPS models which talk
   serial-protocol modbus protocol. [PR #3228]

 - Introduced a new NUT driver named `nut-upower` which provides support
   for monitoring UPS and battery devices managed by the UPower daemon
   via D-Bus. This also introduces a new category of drivers that talk to
   operating system services to obtain power state information. [PR #3279]

 - `upsmon` client updates:
   * Make sure an `FSD` notification is issued for each UPS when this primary
     `upsmon` instance sets it (and does not return to usual data processing
     loop to see and report it like secondaries do). This allows a `NOTIFYCMD`
     such as `upssched` on the primary to handle the pending power outage
     (e.g. begin stopping heavy services) even while `upsmon` waits for the
     secondaries to complete their shutdowns and log out of the `upsd` data
     server. [issue #3003, PR #3110]

 - `configure` script updates:
   * For ages, most recipes for building NUT had customized the `sysconfdir` to
     be `/etc/nut`, which is not exactly the *system* configuration directory.
     This is finally deprecated, with new `--with-confdir` configuration option
     taking over the role of a full path to configuration files (by default
     `${sysconfdir}${confdir_suffix}`), and new `--with-confdir-suffix` allowing
     to specify just `/nut` or `/ups` that would be tacked onto the default
     `${sysconfdir}` to resolve the `${confdir}`. Default behavior should be
     same as with previous builds: if `sysconfdir` is customized (or `prefix`
     is kept at built-in default), the `confdir_suffix` will default to empty;
     otherwise it assumes the value of `/${PACKAGE_NAME}` to become `/nut` in
     most cases. A `--with-confdir-examples` option was also introduced, to
     help distributions that place `*.conf.sample` files into docs or other
     locations. [#3131]
   * The `configure` script would now probe (if it can) the operating systems
     for more user and group account names, such as `upsmon`, `nutmon`, `ups`,
     `nut` (last hit wins, separately for user and groups accounts) settling
     on one of those if detected instead of `nobody` (and optionally `nogroup`).
     It would also warn if `nobody` or `nogroup` end up being used for a build.
     [#3173]
   * Default `PIDPATH` is now more strictly `/var/run`, unless building on a
     system conforming to FHS-3.0 standard where that location is absent or
     is a symlink, while `/run` exists and is a true directory. [#3099]
   * Introduced `--with-python{,2,3}-modules-dir` to specify PyNUT(Client)
     module installation location (for module-named dir to be created under
     it), if not bundling with NUT-Monitor UI app. By default the respective
     interpreter's 'site-packages' or 'dist-packages' location will be used,
     so you may have to adjust search paths for any other values. [#3062]
@
text
@$NetBSD: patch-configure,v 1.1 2025/09/10 11:08:57 jperkin Exp $

Disable special manual page handling on SunOS.

--- configure.orig	2026-04-26 11:40:29.191919966 +0000
+++ configure
@@@@ -27390,8 +27390,6 @@@@ DEFAULT_MAN_DIR_AS_BASE='yes'
 
 case "${target_os}" in
     solaris*|sunos*|SunOS*|illumos*)
-                                                                        DEFAULT_MAN_SECTION_CMD_SYS="1m"
-        DEFAULT_MAN_DIR_AS_BASE="no"
         ;;
 esac
 
@


1.1
log
@ups-nut: Fix build and install on SunOS.
@
text
@d1 1
a1 1
$NetBSD$
d5 1
a5 1
--- configure.orig	2025-09-10 10:50:55.717222074 +0000
d7 1
a7 1
@@@@ -25118,8 +25118,6 @@@@ DEFAULT_MAN_DIR_AS_BASE="yes"
d11 1
a11 1
-        DEFAULT_MAN_SECTION_CMD_SYS="1m"
@