meson links more libs into libpulsecommon, that autotools didn't
Summary
When using meson, libpulsecommon brings in GTK and GLIB:
Control files of package libpulse0: lines which differ (wdiff format)
---------------------------------------------------------------------
Depends: libasyncns0 (>= 0.3), {+libatk1.0-0 (>= 1.12.4),+} libc6 (>= 2.29), {+libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.2.4),+} libdbus-1-3 (>= 1.9.14), {+libgdk-pixbuf-2.0-0
(>= 2.22.0), libglib2.0-0 (>= 2.16.0), libgtk-3-0 (>= 3.0.0), libharfbuzz0b (>= 0.6.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0),+} libsndfile1 (>= 1.0.20), lib
systemd0, [-libwrap0-] {+libx11-6, libx11-xcb1+} (>= [-7.6-4~),-] {+2:1.7.0),+} libxcb1
Installed-Size: [-971-] {+975+}
This is with 14.2 because 14.99 does not have autotools to compare. 14.99 vs 14.2 looks like this:
Control files: lines which differ (wdiff format)
------------------------------------------------
Depends: libasyncns0 (>= 0.3), {+libatk1.0-0 (>= 1.12.4),+} libc6 (>= 2.29), {+libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.2.4),+} libdbus-1-3 (>= 1.9.14), {+libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.16.0), libgtk-3-0 (>= 3.0.0), libharfbuzz0b (>= 0.6.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0),+} libsndfile1 (>= 1.0.20), libsystemd0, libwrap0 (>= 7.6-4~), {+libx11-6, libx11-xcb1 (>= 2:1.7.0),+} libxcb1
Installed-Size: [-971-] {+995+}
Version: [-14.2-2-] {+14.99.1-1+}
Steps to reproduce
Build with meson and glib and gtk.
What is the current bug behavior?
GLib and GTK are linked into libpulsecommon
What is the expected correct behavior?
GLIB and GTK are not linked into libpulsecommon. I suspect autotools was correct, because weak references are usually for non-required dependencies. If I'm wrong, then this issue just needs to be closed.
Edited by Felipe Sateler