[Pkg-libvirt-maintainers] Bug#679074: Bug#679074: Please separate the init scripts for a system-wide libvirtd from the binaries usable for a per-user libvirtd

[Guido Günther]

severity 679074 wishlist
thanks

On Tue, Jun 26, 2012 at 01:05:36AM -0700, Josh Triplett wrote:
> 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.

Does it really make sense to split out the init script? Wouldn't
disabling the daemon also do the trick? 
I'm not yet convinced this is the right way forward.
Cheers,
 -- Guido