[Pkg-libvirt-maintainers] Bug#679074: Please separate the init scripts for a system-wide libvirtd from the binaries usable for a per-user libvirtd
Josh Triplett
josh at joshtriplett.org
Tue Jun 26 08:05:36 UTC 2012
Package: libvirt-bin
Severity: normal
libvirt-bin currently includes both the libvirtd binary (and other
binaries) and the init scripts to start a system instance of libvirtd.
However, many applications using libvirt only need a per-user instance
of libvirtd, not a system instance. For instance, gnome-boxes currently
depends on libvirt-bin to get libvirtd, but it doesn't need the system
instance. According to gnome-boxes upstream, "you can connect to remote
instances, but the only thing that is sanely integrated in the UI is
creating local VMs in a per-user libvirtd". (Anything else, including
the system instance, requires hand-entering a libvirt URI.)
So, please split the init scripts for a system-wide libvirtd instance
into a separate package from the binaries.
Thanks,
Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
More information about the Pkg-libvirt-maintainers
mailing list