Oh, thanks for the inadvertent bump. It seems my headache of the month is NUT packaging, with OmniOS long backlogged. Over 3 years networkupstools/nut #1498 to be exact.

In my defense, OI recipe has also lagged behind NUT releases for a while, as I was fixing its deployment configurability to avoid some complicated patches that OI had to maintain. I hope NUT v2.8.4 is much better in this regard, to make recipe updates easier.

Anyhow, reading through github.com/omniosorg/omnios-extra/blob/master/README.md now. Wondering if there is support for delivering multiple packages from some source downloaded, configured and built once (so one build.sh, many *.p5m files)?

Also I see (I think) a number of repetitive typos like "architecture INdependent SOMEVAR[i386]" -- to me looks like it is exactly the opposite, "architecture-dependent", no?

The multi-package part of NUT is partially warranted by separation of server/client/devel layers, where not everyone wants everything to conserve footprint, and partially by different dependency trees of certain drivers (e.g. some pull in libusb, others net-snmp, others libxml, and a few other groups like that). So again to conserve footprint, NUT deliveries usually split packages so there is possibility to install what you need

hardware, and not pull in a lot of cruft you don't need or use.

Oh, clicking through the dirs got to the end of alphabet, and zabbix has 3 p5m's