<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">On Aug 21, 2024, at 12:34 PM, Heath Smith via Nut-upsuser <nut-upsuser@alioth-lists.debian.net> wrote:<br><div><blockquote type="cite"><br class="Apple-interchange-newline"><div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">1) Who is deciding what goes in to fink and port packages? Do the maintainers of NUT have any say with fink, Mac Ports, and Home Brew (for MacOs machines)?</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"></div></blockquote></div>As Jim mentioned, the distributions like Fink and MacPorts are free to choose the subset of dependencies that they can easily handle.<div><br></div><div>Speaking as someone who coincidentally maintained the NUT package in Fink for a few years, it can be tricky to strike a balance between complexity and maintainability, and altering that dependency chain usually takes quite a bit of testing. I no longer have a working Fink install, so I would have to rely on others to test any changes.</div><div><br></div><div>That said, since Fink moved their package tree to Git a few years ago, it is not too hard to maintain a patch against upstream to trim down the dependencies. If you don't need the Eaton NetXML driver and its dependencies like neon, don't build it. You can change any "BuildDepends: foo" to a "BuildConflicts: foo", and remove the splitoff that packages that up (e.g. <a href="https://github.com/fink/fink-distributions/blob/master/10.9-libcxx/stable/main/finkinfo/net/nut.info#L225">https://github.com/fink/fink-distributions/blob/master/10.9-libcxx/stable/main/finkinfo/net/nut.info#L225</a> ). Sometimes there are ./configure options that need to be removed as well, but usually the BuildConflicts will prevent the library from being visible to the configuration process.</div><div><br></div><div>Similarly, low-level USB support on MacOS has been withering away for some time now. It is especially difficult to detach the incumbent USB HID PDC driver, to the point that I wrote a separate NUT driver (<a href="https://networkupstools.org/docs/man/macosx-ups.html">macosx-ups</a>) to read from the system power monitoring code. libusb doesn't have a ton of dependencies, but it too is a candidate for the chopping block, especially if you are just monitoring a remote UPS on non-Mac hardware.</div><div><br></div><div>I'm not sure what that patch process looks like for MacPorts or Homebrew.</div><div><br></div><div>-- </div><div><div>Charles Lepple<br>clepple@gmail</div></div></body></html>