I'm considering dropping the monolithic libvirtd in future versions of SUSE
distros, which got me to checking the usability of -Ddriver_libvirtd=disabled.
I found it's not very usable :-). This series if an RFC attempt to rectify
the situation. I'm not sure if we should build the various "common"
components unconditionally as this change does, or only if the monolithic
libvirtd and/or one or more modular daemons are also being built.

Thanks for any comments!

Jim Fehlig (2):
  build: Fix build with libvirtd disabled
  spec: Add option to enable/disable libvirtd

 docs/manpages/meson.build |  10 +-
 libvirt.spec.in           |  25 +++-
 meson.build               | 209 +++++++++++++---------------
 meson_options.txt         |  14 +-
 src/access/meson.build    |   3 -
 src/locking/meson.build   | 281 +++++++++++++++++++-------------------
 src/logging/meson.build   | 104 +++++++-------
 src/meson.build           | 200 +++++++++++++--------------
 src/remote/meson.build    | 174 +++++++++++------------
 src/security/meson.build  |   2 +-
 src/util/meson.build      |  24 ++--
 tools/meson.build         |  26 ++--
 12 files changed, 526 insertions(+), 546 deletions(-)

-- 
2.51.0