[Pkg-libvirt-maintainers] Bug#508606: Split virsh to separate package

[Tuomas Jormola]

Package: libvirt-bin
Version: 0.5.1-2
Severity: wishlist
Tags: patch

Hi,

I think that it would be better to split virsh out from libvirt-bin to
its own packge. Reasoning being libvirtd works fine without local virsh
and that virsh has plenty of uses for remote administering of
hypervisors. On the admin machine you don't necessarily want or need
libvirtd binary at all. One could use virsh on a machine running an
architechture where virtualization is not even supported. In my
environment I only have one machine running virtual machines but several
machines that are used to administer the hypervisor remotely using virsh,
and I hate hate having libvirtd cruft installed on these machines.
		 
The attached patch creates virsh package. Depending your taste, you
might want to make libvirt-bin depend on virsh instead of just
recommending it. Technically, it doesn't require virsh to operate, and
thus it shouldn't depend on the package, but some users may encounter
loss of functionality if virsh suddenly disappears from their system
when upgrading libvirt-bin and not installing all the recommended
packages by default.

If accepted, also maybe libvirt-bin package should be renamed to
libvirtd, as currently libvirtd is the only binary left in the
package...

-- 
Tuomas Jormola <tj at solitudo.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: virsh-package.diff
Type: text/x-diff
Size: 2255 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20081213/fcab1b91/attachment.diff