<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#c9">Comment # 9</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:pierre-bugzilla@ossman.eu" title="Pierre Ossman <pierre-bugzilla@ossman.eu>"> Pierre Ossman</a> <pre>This has been lingering a while, but I'd like to get this sorted out. :) As I see it, there are three options: 1. Keep disk and runtime size small This is the original approach, and what my earlier patch does. I.e.: - Clients use libpulse and libpulsecommon - Servers use libpulsecore and libpulsecommon IOW, nothing the client needs in libpulsecore and nothing the server needs in libpulse. 2. Keep disk size small, and less confusing structure - Clients use libpulse - Servers use libpulse and libpulsecore Basically the same as 1, just that libpulsecommon is merged with libpulse. Nothing will really change for clients, but servers will be forced to load a slightly larger library. (And only shipping the server still means shipping some client stuff) 3. Protect API - Clients use libpulse - Servers use libpulsecore Here we duplicate code between libpulse and libpulsecore, but gain the ability to lock down the exported symbols in libpulse so that no one abuses the API. I can be prepared to implement this. We just need to decide on which one. :) 3 seemed to be the preferred from David at least?</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>