<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - daemon shouldn't depend on libpulse" href="https://bugs.freedesktop.org/show_bug.cgi?id=55180#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - daemon shouldn't depend on libpulse" href="https://bugs.freedesktop.org/show_bug.cgi?id=55180">bug 55180</a> from <a class="email" href="mailto:david.henningsson@canonical.com" title="David Henningsson <david.henningsson@canonical.com>"> David Henningsson</a> <pre>It looks like the meaning of these libraries have changed over time. Previous meaning is the one Pierre says: libpulse for client, libpulsecore for server, libpulsecommon for both. Current meaning is: libpulse contain public API functions for clients. libpulsecommon contains other functions internally used by libpulse, pulseaudio and libpulsecore. If we need to bring back the old meaning without losing the new meaning, it sounds like we would need to split libpulsecommon into libpulsecommon-public and libpulsecommon-hidden?</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>