<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - pulseaudio's use of sys/capability.h is non-POSIX" href="https://bugs.freedesktop.org/show_bug.cgi?id=72580#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - pulseaudio's use of sys/capability.h is non-POSIX" href="https://bugs.freedesktop.org/show_bug.cgi?id=72580">bug 72580</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>We treat all other dependencies in the same way: if the user didn't enable or disable an optional feature explicitly, then it's enabled or disabled depending on whether it's available in the system or not. While I didn't come up with this scheme, I think it's a good way to deal with optional dependencies. I want ./configure without arguments to just work, as long as all mandatory dependencies are satisfied. At the end of configure, we print a list of features that are enabled or disabled. Capability support isn't currently in that list, so that could be fixed. Since capabilities are a security feature, it might be a good idea to make an exception in this case, and require explicit --without-caps to make sure that the user really wants to build PulseAudio without capability support, but that should only be done on platforms on which capabilities are supported. We don't support capabilities on Windows, for example, and I don't want to require all Windows users to pass --without-caps.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>