No symlink for libusb.so to libusb.so.1 for -lusb about smartos-live

The platform does not deliver the compilation symlink for a reason: this is not a supported interface. It also doesn't deliver the necessary headers, so it's unclear where apcusbd is getting that from. Do not build against any library in /usr/lib or /lib that lacks a compilation symlink; doing so may result in your applications failing at any time in the future. Instead, use pkgsrc or build your own copy.

libusb is not used by anything in the platform itself, so I'm using this ticket to remove it (the lack of headers and compilation links means it was never usable in the first place). I've opened a separate Joyent ticket, DATASET-426, to track the request for a usable libusb. Feel free to ping me if you have further questions.

In trying to understand the correct solution to the broader problem, we need to know what the use case was here. Were you trying to use apcusbd in a zone? If so, how were you planning to have it obtain its input data from the UPS(es)? If you were trying to install it in the global zone, what features did you actually need from it?

[enmand]

It was quite some time ago that we had this issue, that I can't completely recall the information, but I'll give it a shot:

I believe we were attempting to run it in the global zone. I believe we were looking at the Solaris version of apcusbd to preform a "safe-shutdown" of the global zone.

Ok, the conclusion is that this library should be removed; this isn't supported on SmartOS (nor Smart DataCenter), and using the pkgsrc version won't work because it's incompatible. The library itself was vestigial. If you need direct hardware connection to UPSs, your Joyent support rep can work with you to scope the feature and get it added to the roadmap.

This has been removed in fa1dcf1.