nut-driver@instances
and the nut-driver-enumerator to manage their population), as well as
updated Python 2 and Python 3 support (again, maybe dictating different
package groups) as detailed below.
--with-dev and so may impact upsclient and nutclient (C++) consumers.
At the very least, binaries for those consumers should be rebuilt to remain
stable with NUT 2.8.0 and not mismatch int-type sizes and other arguments.
nutdrv_qx framework
for USB and Serial connected devices, not as updates/clones of older e.g.
blazer family and bestups. Sources, man pages and start-up messages
of such older drivers were marked with "OBSOLETION WARNING".
do_convert_deci flag. See
docs/man/netxml-ups.txt for details.
pkg-config by
default (if present), rather than net-snmp-config(-32|-64) script(s) as
the only option available previously. The scripts tend to specify a lot
of options (sometimes platform-specific) in suggested CFLAGS and LIBS
compared to the packaged pkg-config information which also works and is
more portable. If this change bites your distribution, please bring it up
in https://github.com/networkupstools/nut/issues or better yet, post a PR.
Also note that ./configure --with-netsnmp-config(=yes) should set up the
preference of the detected script over pkg-config information, if both
are available, and --with-netsnmp-config=/path/name would as well.
dummy-ups can now specify mode as a driver argument, and separates the
notion of dummy-once (new default for \*.dev files that do not change)
vs. dummy-loop (legacy default for *.seq and others) [issue #1385]
*.dev
files to work as a looping sequence with a TIMER keywords to change
values slowly; now such files should get processed to the end once.
Specify mode=dummy-loop driver option or rename the data file used
in the port option for legacy behavior.
Use/Test-cases which modified such files content externally should
not be impacted.
Python: scripts have been updated to work with Python 3 as well as 2.
NUT-Monitor script
and nut-monitor.desktop) are still delivered, but now cover a wrapper
script which detects the environment capabilities and launches the best
suitable UI implementation (if both are available).
[D#] prefix to log entries with level > 0
so if any scripts or other tools relied on parsing those messages
making some assumptions, they should be updated
TRACKING ID to be used with
an INSTCMD or SET VAR requests; for details see docs/net-protocol.txt
and docs/sock-protocol.txt
--with-augeas-lenses-dir configure option.