net-mgmt/smartctl_exporter: update to 0.15.0
Upstream's go.mod now declares go 1.26, and Go 1.23 and later only
import vendored packages that are listed in vendor/modules.txt. Ship
a generated files/modules.txt and install it in post-extract, and add
a generate-modules-txt maintenance target to regenerate it together
with GH_TUPLE.
Fix the rc.d script:
- smartctl_exporter_syslog is now evaluated with checkyesno; any
non-empty value, including NO, used to enable syslog.
- Quote the device exclude regexp, so that shell metacharacters
such as ( and | no longer break the command line.
- Quote the entries of smartctl_exporter_devices, so that a device
type can be given after a semicolon ("/dev/mfi0;megaraid,1").
While here, set the version reported by the binary and by the build
info metric, and document smartctl_exporter_args.
Changes: https://github.com/prometheus-community/smartctl_exporter/releases/tag/v0.15.0
net-mgmt/smartctl_exporter: fix NVMe device discovery in rc.d script
Switch from a fixed device list (via geom disk status) to smartctl_exporter's
built-in auto-discovery with periodic rescan. The old approach had two issues:
nda(4) devices can't be queried for SMART data (the nvme(4) controller must be
used instead), and a fixed list doesn't detect hot-plugged devices.
Add smartctl_exporter_device_exclude defaulting to "nda" to filter NVMe CAM
devices from auto-discovery. Users can still override with
smartctl_exporter_devices in rc.conf for an explicit device list.
PR: 297170
Reported by: ivy
net-mgmt/smartctl_exporter: add LICENSE_FILE, fix redundant sed flag
Add LICENSE_FILE to point to the actual license file in the source tree.
Remove redundant -i '' flag from REINPLACE_CMD (already included in
REINPLACE_CMD definition).
PR: 288167
many: Unpin Go ports
* Ports that were pinned to a deprecated version of Go (1.23 or older)
have been unpinned.
* Ports that were pinned to a still-supported version of Go (1.24 or
newer) have been converted to requesting that as their minimum Go
version.
* Ports that had been forcibly deprecated for pinning an expired Go
version have been undeprecated.
many: Unsupported Go dep; deprecate and schedule for removal
There are about 75 ports that depend on old, unsupported Go
versions. I've scheduled those Go versions for deletions on
2025/01/01, and so these ports are scheduled for removal on
that same day.
HOWEVER....
Likely NONE or VERY VERY FEW of these ports will actually need
to be deleted! This stems from a misunderstanding:
When go.mod says "go 1.23", it means that it requires AT LEAST
go-1.23. Locking a port to a specific go version should almost
never happen; it is reserved for when a package absolutely
(Only the first 15 lines of the commit message are shown above )
