Jim Klimov
Jim Klimov
A practical search on a test system does use `realpath()` (where available) and practically use the ultimate file name when it looks at a symlink (which does exist): ```` 0.002097...
Running some experiments with another lib that is easier to fiddle with (NUT only built in this system, not installed into common paths, so its own `libupsclient` is not resolved...
As a side note, this may also be a concern for DMF effort (currently awaiting its destiny in another branch): * https://app.circleci.com/pipelines/github/jimklimov/nut/1663/workflows/39cda40a-9cdd-437f-bc47-8ac693f290e0/jobs/4951 after PR #2275 for issue track #1316 ````...
Thanks for confirming this is more wide-spread ;( and also on the radar for so long...
My concern would be about picking a somewhat random library this way. Say `libusb.so.(0|1)` on some system meant the two different ABIs of separate generations of the library. Linking would...
Seems to work, even on a Mac: ```` :; LD_LIBRARY_PATH="`pwd`/clients/.libs" ./tools/nut-scanner/nut-scanner -D ... 0.000915 [D1] Looking for lib libusb-1.0.0.dylib, found /usr/local/Cellar/libusb/1.0.27/lib/libusb-1.0.0.dylib 0.000933 [D1] nutscan_init: get_libname() resolved '/usr/local/Cellar/libusb/1.0.27/lib/libusb-1.0.0.dylib' for LibUSB, loading...
Currently we do not make snapshot packages (the idea is in backlog though), so your best shot for the latest and greatest features (and mishaps) is https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests
With #2532 in place, it seems all reasonable goals of this issue have been achieved.
Currently, to get recent changes (master branch; the recent change above is not part of any numbered release yet) custom-compiling is the only official option; the https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests page (and docs...